Skip to main content

Use Cases

This page contains real-world workflows using the Job Posting Search API. Each use case is designed to be:
  • βœ… Easy to copy and run
  • πŸ”§ Simple to customize
  • 🎯 Aligned with common customer goals

How to Use These Examples

  1. Copy the example
  2. Replace inputs (e.g. location, company_website)
  3. Run the request
Need help getting started?See the full Quickstart guide to make your first Job Posting Search API request.Looking for more patterns? Browse the Examples page for a library of additional query examples.
Credit Usage ReminderEach job posting returned costs 1 credit.If your query may return many results, start with a small size (e.g. 10) and paginate using scroll_token.

🧭 Keep a Job Board Up to Date

Goal: Keep the job postings shown in your job board fresh as users search and browse. Recommended workflow: Query the Job Posting API when a user runs a search, filter to active postings, and paginate with scroll_token. This gives users current results without requiring a full background refresh of every matching job. When to use this:
  • Power a live job board or search experience
  • Keep displayed jobs fresh
  • Avoid refreshing every possible matching posting upfront
Python
To load the next page, send the same query with the latest scroll_token:
Python

B. Full Refresh: Pull All Active Matches on a Schedule

Use this when your use case needs a complete refreshed result set for a fixed filter, such as all active engineering jobs in a country.
This strategy is simple and keeps your data current, but it can return many records. Start with a small size, estimate result volume with total, and paginate using scroll_token.
Python

Customize This

  • Replace location with your target geography, such as "united states", "california", or "san francisco, california, united states".
  • Change the title filter from title to a structured field such as title_role, title_sub_role, or title_levels.
  • Keep is_active set to true when you only want active postings.
  • Adjust size based on your UI. A search results page often starts with 10-20 records, while a scheduled refresh can use up to 100 records per request.
  • Use scroll_token to load additional pages until you have enough results or pagination is complete.

🌍 Get All Job Postings in a Country

Goal: Retrieve job postings for a specific country. When to use this:
  • Analyze hiring trends by region
  • Build geo-based prospecting lists
  • Monitor hiring activity in new markets

Example

Python

Customize This


🏒 Get All Job Postings from a Company

A. Single Company

Goal: Retrieve all job postings for a specific company. When to use this:
  • Track hiring activity for a target account
  • Monitor competitor hiring
Python

B. Multiple Companies (Target Account List)

Goal: Retrieve job postings across a list of companies. When to use this:
  • Analyze hiring across target accounts
  • Build outbound prospecting signals
  • Compare competitors
Python

Customize This


πŸ”— Find Companies β†’ Then Get Their Job Postings

Goal:
  1. Find companies matching a criteria
  2. Retrieve all job postings for those companies
Example scenario:
Find companies headquartered in San Francisco, CA with >10k employees, then get all their job postings.

Step 1: Find Companies

Use the Company Search API to retrieve companies in your target region.
Python
(Example Results)
Python

Step 2: Get Job Postings for Those Companies

Python

Why This Matters

This pattern is powerful for:
  • Territory-based prospecting
  • Market mapping
  • Lead generation workflows

πŸ“ˆ Use Job Postings as an Intent Signal

Goal: Identify companies showing hiring intent for a specific function so you can prioritize outreach. Example: Find companies with newly posted SDR roles since April 9, 2026.

Example

Python

Why This Works

This pattern is useful when job postings act as a buying or growth signal. If a company is actively hiring SDRs, AEs, recruiters, or engineers, that can indicate:
  • Team expansion
  • New budget or headcount
  • Operational pain points they may want to solve
  • A reason to prioritize outreach with a relevant message

Customize This

You can adapt this pattern for:
  • Other functions like title = "account executive", "recruiter", or "gtm engineer"
  • Search for keywords in the description description like "salesforce", "python", or β€œdatabricks".
  • Different recency windows using first_seen_min
  • Regional targeting by adding location
  • Account-based monitoring by layering on company_id or company_website

πŸš€ What to Try Next

For a comprehensive list of query patterns, see the Examples page.