$5 free Limited time. Sign up to activate. Get your $5 →
How-to · Jobs

How to find job postings by company

Resolve the company to an id once with the organizations autocomplete, then call the job post search with organization_ids, is_active true and date_featured_start. Store each post's id; a scheduled run that sees a new id is a new role.

How to find job postings by companyResolve the company to an id once with autocomplete, then search job posts filtered by that id, active status and a posted-since date. Keep the ids you have seen so only new posts raise an alert.Watch a company's open rolesResolve once, search on a schedule, alert only on new postsExample Corp1Autocomplete: idfree; resolve once and cache the id2Job post searchorganization_idsis_active: truedate_featured_startJOB POSTtitleSenior Data EngineerlocationRemote · USfeatureddate_featuredsourcethe job board it came fromidstore it as seennew id: alertseen id: skipSample values are fictional. Re-posts and expired postsare the two traps to handle.
The seen-id store is the whole watch: a post you have already stored is not a signal.

Free routes and their limits

For one company, once, the careers page is the source of truth. The jobs tab on its professional profile page and a Google Jobs search add the postings syndicated elsewhere. All three are free and none of them tells you what changed since yesterday, which is the only question a watchlist asks.

Page 1 for "job postings api" is vendor pages and vendor lists (fantastic.jobs, Apr 2026, compares six). None shows the one-company task end to end, so that is what follows.

Resolve the company to an id

The job search filters by organization_ids, so first turn the company into an id. The organizations autocomplete takes q as a name or a domain and returns results whose text reads "name - domain", which lets you confirm the right company before you store its id. It is free, limited to 10 requests a second, and you only need to call it once per company.

Organizations autocomplete

curl -G https://api-v2.forager.ai/api/{account_id}/datastorage/autocomplete/organizations/ \
  -H "X-API-KEY: $FORAGER_API_KEY" \
  --data-urlencode "q=example.com"
Sample values are fictionalFields: API reference

The id comes back as a string; the search expects an integer, so convert it.

Filter by team, not just company

A company opening a sales role and a company opening a data team are different signals. The title field takes a boolean query, so watch the team you care about: "data engineer" OR "analytics engineer". The description field takes the same syntax for keywords that do not reach the title.

Watch on a schedule, alert on new ids

  1. Run the search once a day per company with date_featured_start set to the date of your last run, so each run asks for less.
  2. Compare each post's id with the ids you have stored.
  3. Alert on the ids you have not seen, then store them.
  4. Group alerts by organization name so a rep sees "Example Corp opened 4 roles", not four messages.

An empty search_results is not an error. It means nothing new; log it and move on.

Two traps: re-posts and expired posts

A role that was featured again after a quiet month arrives with a new date_featured. If your alert fires on dates, it fires twice; if it fires on ids you have not seen, it fires once. Our rule, a heuristic rather than a field: treat a post with the same title and location as one you stored within the last 90 days as the same role.

An expired post is one that is_active no longer marks as open. Filter with is_active true on the search, and when you count open roles for a company, count only posts that were active on the last run.

Counting first

Before you page through a big company's postings, the job search totals endpoint takes the same body and returns counts. Its credit cost is not yet documented in the credit table, so check the docs before you assume it is free.

At scale: the job postings feed

A watchlist of fifty companies is an API job. Hiring velocity across a whole market is a feed job: license the job postings feed, load it into your warehouse on a schedule, and compute openings per company in SQL. The strategy piece on hiring signals is on the product page below.

Questions about this guide

Can I search job postings by company name?

Yes, in two steps. The organizations autocomplete turns a name or a domain into an id, with a text field that reads "name - domain" so you can confirm the match. Pass that id in organization_ids to the job search.

Which job sources are included?

Each post's source field says which job board it came from. To filter, set job_source to one of the values the docs list today.

How do I know a job post is still open?

Search with is_active true. When you count open roles for a company, count only posts that were active on your last run, and treat a post that stops appearing as closed.

How often should I poll for new postings?

Once a day per company is enough for a sales or recruiting watchlist. Set date_featured_start to your last run date so each run is small, and alert on ids you have not seen rather than on dates.

Is a job post personal data?

No. A job post is a company's public listing: title, location, date, source and the organization. Recruiter names and contact details are not part of the response.

What does a job postings search cost?

A job search costs 2 credits per request, charged whether or not posts come back. The organizations autocomplete that resolves the company is free.

What does the job postings API cost for teams following this guide?

Job postings API: 2 credits per request, charged whether or not data comes back. 1,000 job search requests use 2,000 credits: about $27 of Starter credits month to month, or about $20 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

Am I charged when nothing is found?

Yes. Job postings API is charged per request, whether or not data comes back. Only mobile and email lookups are free when nothing is found, so try your inputs on a small run before you scale.

Can teams following this guide test the job postings API for free?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

How do I know the data is right?

The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

How is the data sourced, and what about privacy?

Bring your legal and security questions to a call with our team, and we take you through how Forager data is sourced and the terms that cover job postings API for teams following this guide. Forager's privacy policy is public, and anyone can send a request about their own personal data through the consumer rights form on forager.ai.

Do I need a subscription?

Not to test: a free account comes with $5 in credits. To keep using job postings API, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Keep reading

Start building

Run it on your own records

Create a free account, start with $5 in credits and try the lookups in this guide on people and companies you already know.

  • $5 free credits
  • No credit card
  • Run your sample
Platforms and teams that build on Forager
  • Clay
  • Juicebox
  • Nooks
  • Andela
  • HubSpot
  • SeekOut