Company Hiring Signals Tracker API

API ID 15124

Hiring snapshot for a company from its public ATS board: open roles, roles by department, location and seniority, new roles and remote share.

812 ms avg response

API Documentation

Endpoints

Request
Returns a hiring snapshot for one company found by domain, board link or slug: open roles, breakdowns and newly posted roles.
Endpoint ID: 40354
GET https://zylalabs.com/api/15124/company+hiring+signals+tracker+api/40354/hiring+signals+for+a+company
INPUT PARAMETERS

Hiring signals for a company — Endpoint Features

Object Description
company Required Company domain, ATS board link or board slug, for example notion.so.
domain Optional Company domain, as an alternative to company.
board Optional ATS board link, for example a Workday or Greenhouse career site.
department Optional Count only roles whose department contains this text.
location Optional Count only roles whose location contains this text.
maxCompanies Required Maximum companies per call, 1 to 8. Default 8.
maxNewRoles Required Newly posted roles to list, 0 to 100. Default 25.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

company
domain
board
department
location
maxCompanies
maxNewRoles
API EXAMPLE RESPONSE
JSON
{
    "count": 1,
    "errorCount": 0,
    "companies": [
        {
            "recordType": "company",
            "company": "Notion",
            "companyKey": "domain:notion.so",
            "domain": "notion.so",
            "ats": "ashby",
            "atsList": [
                "ashby"
            ],
            "boardTokens": [
                "notion"
            ],
            "sourceUrls": [
                "https://jobs.ashbyhq.com/notion"
            ],
            "discoverySource": "slug_probe",
            "input": [
                "notion.so"
            ],
            "totalOpenRoles": 169,
            "totalOpenRolesSource": "ats_total",
            "cacheAgeSeconds": 0,
            "source": "live",
            "cachedAt": "2026-11-20T19:01:49Z",
            "totalOpenRolesScope": "board",
            "lastFetchedAt": "2026-11-20T19:01:49Z",
            "rolesByDepartment": [
                {
                    "name": "Sales",
                    "count": 68
                },
                {
                    "name": "Outcomes Architect",
                    "count": 21
                },
                {
                    "name": "Engineering",
                    "count": 17
                },
                {
                    "name": "People",
                    "count": 15
                },
                {
                    "name": "Early Career",
                    "count": 10
                },
                {
                    "name": "Marketing",
                    "count": 10
                },
                {
                    "name": "Revenue Operations & Strategy ",
                    "count": 8
                },
                {
                    "name": "Customer Experience",
                    "count": 6
                },
                {
                    "name": "Finance",
                    "count": 5
                },
                {
                    "name": "Security",
                    "count": 3
                },
                {
                    "name": "User Research and Product Operations",
                    "count": 2
                },
                {
                    "name": "Product Management",
                    "count": 2
                },
                {
                    "name": "Legal",
                    "count": 1
                },
                {
                    "name": "Business Technology",
                    "count": 1
                }
            ],
            "rolesByLocation": [
                {
                    "name": "San Francisco, California",
                    "count": 63
                },
                {
                    "name": "Dublin, Ireland",
                    "count": 35
                },
                {
                    "name": "Tokyo, Japan ",
                    "count": 21
                },
                {
                    "name": "New York, New York",
                    "count": 18
                },
                {
                    "name": "Singapore",
                    "count": 6
                },
                {
                    "name": "Seoul, South Korea",
                    "count": 6
                },
                {
                    "name": "London, United Kingdom",
                    "count": 6
                },
                {
                    "name": "Paris, France",
                    "count": 5
                },
                {
                    "name": "Munich, Germany",
                    "count": 4
                },
                {
                    "name": "Sydney, Australia",
                    "count": 2
                },
                {
                    "name": "Hyderabad, India",
                    "count": 2
                },
                {
                    "name": "Atlanta, Georgia",
                    "count": 1
                }
            ],
            "rolesBySeniority": [
                {
                    "name": "unspecified",
                    "count": 109
                },
                {
                    "name": "manager",
                    "count": 38
                },
                {
                    "name": "senior",
                    "count": 8
                },
                {
                    "name": "intern",
                    "count": 5
                },
                {
                    "name": "director",
                    "count": 4
                },
                {
                    "name": "junior",
                    "count": 3
                },
                {
                    "name": "c_level",
                    "count": 1
                },
                {
                    "name": "staff",
                    "count": 1
                }
            ],
            "topHiringTeams": [
                {
                    "name": "Sales",
                    "count": 36
                },
                {
                    "name": "Solutions Consultant",
                    "count": 32
                },
                {
                    "name": "Outcomes Architect",
                    "count": 21
                },
                {
                    "name": "Engineering",
                    "count": 17
                },
                {
                    "name": "People",
                    "count": 15
                },
                {
                    "name": "Early Career",
                    "count": 10
                },
                {
                    "name": "Marketing",
                    "count": 10
                },
                {
                    "name": "Revenue Operations & Strategy ",
                    "count": 8
                },
                {
                    "name": "Customer Experience",
                    "count": 6
                },
                {
                    "name": "Finance",
                    "count": 5
                }
            ],
            "remoteCount": 97,
            "remoteShare": 57.4,
            "newRolesSinceLastRun": null,
            "closedRolesSinceLastRun": null,
            "newRoles": [],
            "previousSnapshotAt": null,
            "velocityPerWeek": 9,
            "velocitySource": "posted_dates",
            "rolesPostedLast7Days": 9,
            "rolesPostedLast14Days": 28,
            "velocityIsLowerBound": false,
            "rolesPostedLast14DaysIsLowerBound": false,
            "newRoles7dIsLowerBound": false,
            "newRoles14dIsLowerBound": false,
            "totalOpenRolesIsLowerBound": false,
            "sampleScope": "full",
            "hiringMomentumScore": 77,
            "sourceRead": true,
            "error": null,
            "errorType": null,
            "message": null,
            "scrapedAt": "2026-11-20T19:01:49.860531+00:00"
        }
    ],
    "errors": [],
    "sourceRead": true,
    "source": "live",
    "cachedAt": "2026-11-20T19:01:49Z",
    "cacheAgeSeconds": 0
}
Hiring signals for a company — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15124/company+hiring+signals+tracker+api/40354/hiring+signals+for+a+company?company=notion.so&maxCompanies=1&maxNewRoles=3' --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 Hiring Signals Tracker 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

Hiring snapshot for a company from its public ATS board: open roles, roles by department, location and seniority, new roles and remote share.

Company Hiring Signals Tracker API FAQs

A snapshot of how a company is hiring right now: total open roles, roles by department, location and seniority, top hiring teams, new roles and remote share.

A company domain, a career board link or a board slug. Workday career sites are supported through the board parameter.

The API returns HTTP 404 with a message. Send the career page link through the board parameter to point it to the right board.

Boards are read live. A short cache may serve repeated identical requests and the response shows source and cacheAgeSeconds.

Sales teams looking for companies that are growing, investors tracking headcount trends and recruiters watching competitors.

It returns one company’s hiring snapshot, including total open roles, department and location breakdowns, seniority data, newly posted roles, top hiring teams, and remote-work share.

The response is a JSON object containing `count`, `errorCount`, and a `companies` array. Each company record includes identification, ATS and source details, hiring totals, breakdown arrays, and role-level information.

Submit a company domain, public ATS board link, or board slug. The response may identify the match with fields such as `company`, `domain`, `companyKey`, `boardTokens`, and `sourceUrls`.

`ats` identifies the detected applicant tracking system, while `atsList` lists associated systems. `sourceUrls` shows the public board used. `discoverySource` describes how the board was found, such as `slug_probe`.

`totalOpenRoles` is the number of open positions found. `totalOpenRolesSource` indicates how that total was obtained, and `totalOpenRolesScope` defines its coverage, such as the entire board rather than a filtered subset.

Roles are grouped into breakdown arrays such as `rolesByDepartment`, `rolesByLocation`, and `rolesBySeniority`. Each entry typically contains a category name and its role count, making the data suitable for comparisons and charts.

Use `source` to identify whether the result is live or cached, and `cacheAgeSeconds` to see the cache age. `cachedAt` and `lastFetchedAt` provide timestamps for the stored and most recent source data.

Check `count`, `errorCount`, and the `companies` array before processing results. A successful match contains a company record; empty results or errors should be handled as unavailable public-board data rather than assumed zero hiring.

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