Job Search

The Job Search endpoint lets you find open positions across all supported ATS platforms. Results are pre-filtered to only include jobs that can be submitted through the API — so every job you get back is ready to be passed directly to the Sessions apply endpoint.

This is useful for clients who don't have their own job feed and want to offer end-to-end search-and-apply functionality through a single API.

Search for jobs by title, location, and optional filters. Returns a list of matching jobs with full details including company information, salary data, and direct application URLs.

Each job in the response array contains the following fields. Fields marked Always are guaranteed to be present. Fields marked Nullable may be null when data is not available.

The typical workflow is to search for jobs, let the user select which ones to apply to, and then pass them to the Sessions apply endpoint. The job url field maps directly to the link field in the apply request.

The API automatically excludes jobs that were returned in previous searches for your account within the last 24 hours. Each search only returns fresh, never-before-seen jobs — so you can call the search endpoint repeatedly without worrying about duplicates.

This works by tracking the job IDs returned in your recent search records (within a 24-hour rolling window). When a new search is performed, those job IDs are excluded server-side so results are always fresh.

For Autopilot Recurring sessions, deduplication is even more specific — it filters out jobs that the candidate has already applied to (regardless of success or failure), ensuring each recurring run only applies to genuinely new positions.

Filter parameters (workType, jobType, experienceLevel) accept either a single string or an array of strings. When multiple values are provided, results matching any of the specified values are returned.

If fewer jobs match your filters than the requested results count, the API progressively relaxes filters to find more results. The relaxation order is: salary minimum and company size are dropped first, then experience level and job type, and finally work type. This ensures you always get the most relevant results possible while still meeting your target count.

Note: Hybrid work type is treated as non-remote for filtering purposes, since the underlying job data only distinguishes between fully remote and non-remote positions.

Retrieve a paginated list of your previous job searches. Each record includes the search query, filters used, result count, and how many applications were submitted from that search.

Retrieve a specific search record by ID, including the full jobs array. Use this to show the original search results or to let users select jobs to apply to from a previous search.

Job Search requests count toward your API key's 25 concurrent request limit (shared with Sessions). Each search holds a concurrent slot until the results are fully returned. If you exceed 25 simultaneous in-flight requests, additional requests will receive a 429 response.

For high-volume search use cases, stagger requests or wait for previous searches to complete before sending new ones. See the Rate Limiting guide for details on response headers and retry strategies.