Company Career Pages Jobs API

API ID 15083

Open jobs from company career pages across six applicant tracking systems in one normalized schema. Responses are JSON {count, limit, results[], request id}; errors are

1,361 ms avg response

API Documentation

Endpoints

Request
Reads the public job boards of Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee and returns normalized jobs (newest first). Up to 5 companies and 10 jobs per call (use keyword, location and remote filters to narrow).
Endpoint ID: 40094
GET https://zylalabs.com/api/15083/company+career+pages+jobs+api/40094/open+jobs+from+company+career+pages
INPUT PARAMETERS

Open jobs from company career pages — Endpoint Features

Object Description
company Required Comma-separated board slugs or careers URLs (max 5), e.g. "airbnb,stripe". With "ats" set, slugs are resolved on that ATS; without it every ATS is probed (slower).
ats Optional Applicant tracking system for the slugs.
keyword Optional Comma-separated; keep jobs whose title, department or team contains any (max 10).
exclude Optional Comma-separated; drop jobs containing any of these (max 10).
location Optional Keep only jobs whose location contains this text.
remote Optional Only jobs marked remote.
posted_within_days Optional 0 disables the filter.
include_description Optional Add the job description as plain text (larger response).
limit Optional Maximum jobs returned.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

company
ats
keyword
exclude
location
remote
posted_within_days
include_description
limit
API EXAMPLE RESPONSE
JSON
{
    "count": 1,
    "limit": 1,
    "results": [
        {
            "ats": "greenhouse",
            "companySlug": "airbnb",
            "companyName": "Airbnb",
            "jobId": "8376045",
            "title": "Brand Marketing Intern, France",
            "department": "Intern",
            "team": null,
            "location": "Paris, France",
            "locations": [
                "Paris, France"
            ],
            "remote": null,
            "workplaceType": null,
            "employmentType": null,
            "salary": {
                "min": 25000,
                "max": 25000,
                "currency": "EUR",
                "period": "YEAR",
                "text": "France Annual Pay Range"
            },
            "postedAt": "2026-11-18T17:41:29.000Z",
            "updatedAt": "2026-11-18T17:41:29.000Z",
            "url": "https://careers.airbnb.com/positions/8376045?gh_jid=8376045",
            "applyUrl": "https://careers.airbnb.com/positions/8376045?gh_jid=8376045",
            "descriptionText": "Airbnb was born in 2007 when two hosts welcomed three guests to their San Francisco home, and has since grown to over 5 million hosts who have welcomed over 2 b",
            "scrapedAt": "2026-11-19T13:23:42.525Z"
        }
    ],
    "request_id": "00000000-0000-4000-8000-000000000000"
}
Open jobs from company career pages — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15083/company+career+pages+jobs+api/40094/open+jobs+from+company+career+pages?company=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Company Career Pages Jobs API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Open jobs at company career pages across six applicant tracking systems in one normalized schema.

Company Career Pages Jobs API FAQs

The Company Jobs API aggregates open job listings from company career pages across six different applicant tracking systems (ATS) into a single, normalized schema, simplifying access to job data.

Successful responses are in JSON format and include a 'count' of the jobs found, a 'limit' indicating the maximum number of results returned per call, an array named 'results' containing the job details, and a 'request_id' for tracking.

This API is ideal for job aggregators, recruitment analytics platforms, and internal HR systems that need to display or process a wide range of open positions from various companies without needing to integrate with each ATS individually.

The core value lies in its ability to provide a unified view of job openings from multiple ATS platforms, saving developers time and resources by eliminating the need for separate integrations with each system.

Each object within the 'results' array represents a job and contains normalized fields detailing the job title, description, location, company information, and a direct link to the job posting, among other relevant details.

The API normalizes data from six different ATS platforms into a consistent schema. This means that regardless of the source ATS, the job data you receive will follow the same structure and field definitions.

While the API returns results in batches, the 'count' field in the response indicates the total number of available jobs. You can make subsequent calls, adjusting parameters as needed, to retrieve all job listings if the total exceeds the 'limit' set for a single request.

A normalized schema ensures consistency in the data you receive, regardless of the original applicant tracking system. This significantly simplifies data processing, analysis, and display, as you don't need to write custom logic for each ATS's unique data format.

The API reads Greenhouse, Lever, Ashby and Workable career pages, given a company's board slug. It returns up to 10 jobs per call.

The endpoint reads public career pages powered by Greenhouse, Lever, Ashby, Workable, SmartRecruiters, and Recruitee. The `ats` field identifies the source system for each returned job.

Use the `keyword`, `location`, and `remote` filters to narrow results. You can also query jobs for up to five companies in one request by providing their career-page or board slugs.

Requests use a company slug associated with its public career page or ATS board. In the response, `companySlug` preserves that identifier, while `companyName` provides the readable company name.

Jobs may include a primary `location`, a `locations` array for multiple locations, and `remote` or `workplaceType` values when supplied by the source. These fields can be null when the career page does not publish the information.

When available, `salary` contains normalized `min`, `max`, `currency`, and `period` fields, plus the source’s descriptive `text`. Compensation may be absent or partially populated if the original listing does not disclose it.

Use the combination of `ats`, `companySlug`, and `jobId` as a source-aware identifier. The `url` field links to the job posting, while `applyUrl`, when present, links directly to the application page.

`postedAt` records when the job was posted, and `updatedAt` records the latest reported modification. Both are ISO 8601 timestamps, such as `2026-11-18T17:41:29.000Z`, and can support sorting or change detection.

Treat optional fields such as `team`, `remote`, `workplaceType`, `employmentType`, and `salary` as nullable. If filters match no listings, process the response as an empty `results` array and use `count` to represent the returned match total.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs