Frequently Asked Questions

Is CORS Enabled?

No, we discourage calling this API from the front-end of your application.

How does deduplication work?

We use the following types of deduplication:

• Every job in our database is unique by URL.
• Across all 63 ATS sources, listings with matching title, organization, description, locations, and location_requirements are treated as content duplicates even when their URLs differ. Listings that differ in any of these fields, such as separate versions of a job for different locations, are still returned.
• We have a parameter to remove ATS duplicates from the JB endpoint. We flag jobs in active-jb that are already present in active-ats using two checks: title + organization name + country, and title + LinkedIn company profile + country. Set exclude_ats_duplicate=true to drop the flagged duplicates from the response. This will not remove 100% of the duplicates so we recommend adding another layer of fuzzy deduplication on your end.

Can I search for special characters?

Not literally or reliably. The title, description, location, and _advanced search parameters use full-text search rather than substring matching. Most punctuation is treated as a separator or as search syntax instead of an independently searchable character. For example, terms such as C++, C#, or .NET may be normalized to their alphanumeric portion and can therefore return broader matches. Search for the meaningful alphanumeric term, then filter the returned field for the exact spelling in your application when punctuation matters.

The _advanced parameters also reserve characters such as &, |, !, <, and > as operators. URL-encode these operators when using them as documented in the Advanced Searching Guide.

How many Job Titles / Companies / Locations can I include in my request?

All the characters in the request should be less than 10,000 characters

What is the timeout for an API request?

An API request will timeout after 60 seconds. If your requests timeout regularly we recommend using a smaller time_frame on active-ats or active-jb (e.g. 1h or 24h instead of 6m). We also recommend avoiding description searches with time_frame=6m, or being very specific if you do need them - on active-jb description search is not allowed at all when time_frame=6m and will return a 400 error.