# FAQ

# Frequently Asked Questions

## Is CORS Enabled?
No, we discourage calling this API from the front-end of your application. 

## How does deduplication work?
Our intention is to provide you with as much raw job data as possible, therefore we only do two types of deduplication on our end:
- Every job in our database is unique on their URL. There are some exceptions to this since some ATS can have jobs that are 100% duplicate between several sites. Generally speaking we will provide the jobs as is, even if the ATS posts multiple versions of the job with just a difference in location (common for Greenhouse)
- 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, and title + LinkedIn company-profile match. 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.

## 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.