This is a draft for internal review. It is not legal advice and has not been reviewed by a lawyer. Do not treat it as binding.
Terms of Service
The terms governing use of Reqbeat's metered hiring-signal API.
Version 0.1.0-draft · Effective 28 August 2026 · Last generated September 14, 2026
1. Acceptance
By creating a Reqbeat account or calling the API with an issued key, you agree to these terms on behalf of yourself and, if you're acting for a company, on behalf of that company. Reqbeat is operated by Deal Baker Ltd.
2. The service
Reqbeat sells metered API access to a corpus of aggregated public hiring-signal data — company hiring status, open requisitions, hiring trend and market-demand data, all derived from applicant-tracking-system postings and public job boards. It is not a source of data about individuals: see the Privacy Policy and Data ethics for what the corpus does and does not contain.
The data guarantee, and its limits
- •Every value Reqbeat's API serves about a company or a job posting is read from a public job advertisement — a posting on a company's own applicant-tracking system, on a public job board, or on an aggregator that re-lists them. None of it is bought from a private database or a people-data broker.
- •LinkedIn's public job listings are one of those public sources, and a substantial part of the corpus is read from them. What is read there is the job advertisement, exactly as on any other board. The complete list of fields Reqbeat holds and serves is published at reqbeat.com/data-ethics, and the board a posting was detected on is itself one of those fields — so the origin of any row you are served is something you can inspect, not something you have to take on trust. A company may also be matched internally using a public LinkedIn handle as a join key; that handle is never itself returned.
- •No contact PII of any kind — no name, email address, phone number, or profile of a natural person — is ever served as a field. No field in the API's response schema is a person record. The one thing this cannot promise is the advertisement's own text, which is served verbatim as the employer published it: a contact detail an employer chose to print in their own public advert is in that text. Reqbeat neither extracts it, indexes it, nor builds a person record from it.
- •The corpus that backs Reqbeat's public research pages (reqbeat.com/method, reqbeat.com/data-ethics) is read through a separate, read-only connection that cannot reach a customer's account, usage, or queries at all — enforced at the code level and checked by an automated test on every change.
3. Accounts and API keys
You create an account with a work email; we send a single-use magic link rather than a password. You are responsible for keeping your API key confidential — anyone who holds it can act as you against the API, and usage under your key is billed to your account regardless of who made the call. Revoke a compromised key immediately from your dashboard.
We may suspend or terminate an account that violates these terms, abuses the service, or fails to pay.
4. Fees and billing
Reqbeat is metered on a single billable unit — the sourced company row — in addition to any base tier fee. Watches are included in the plans, and each plan carries its own monthly allowance of delivered change events; a delivered change is charged against that same unit rather than at a separate per-event price.
These terms deliberately quote no rate. The rate that governs at any moment, and each plan's included allowances, are whatever is published at https://reqbeat.com/pricing. That page is regenerated on a fixed cycle and re-reads the current price from our billing system each time, so the figure it shows is at most 3 hours old — still the controlling one, because a number written into this document would never be re-read at all.
Billing is handled by Stripe. You may start on a free or trial tier without a card; to continue past a trial or a usage cap you'll need to add a payment method through your dashboard. We do not store your card details ourselves.
Fees are non-refundable except where required by law or stated otherwise at the time of purchase.
5. Permitted use
You may:
- ✓Use the data returned by the API in your own product or workflow, including output you derive from it.
You may not:
- ✗Attempt to re-identify, link, or associate any data returned by the API with a named individual.
- ✗Use the service to build or seed a competing raw hiring-signal corpus by bulk-extracting the API beyond your metered, intended use.
- ✗Circumvent rate limits, quotas, or metering, including by sharing a single API key across accounts it was not issued to.
- ✗Use the service to discriminate against individuals or companies on a legally protected basis, or for any unlawful purpose.
- ✗Resell or redistribute raw API responses as a standalone data feed, as opposed to output you derive and build into your own product.
Nothing in this section grants you a right in the underlying postings. Reqbeat reads job advertisements published by employers and carried by job boards and aggregators, each of which has its own terms; these terms pass no third-party licence through to you, and what you do with the text and links the API returns is your responsibility.
6. Intellectual property
We retain all rights in the Reqbeat corpus, API, and site. You retain all rights in your own product built on top of the data we return, and in any query, webhook configuration, or other input you provide us.
7. Disclaimer and limitation of liability
The service is provided "as is". Hiring-signal data is inferred from public postings and is inherently probabilistic — we do not warrant that any figure, status, or event the API returns is accurate, complete, or current at the moment you read it.
To the maximum extent permitted by the laws of England and Wales, Deal Baker Ltd is not liable for indirect, incidental, or consequential damages arising from your use of the service, and our total liability for any claim is capped at the fees you paid us in the three months preceding the claim.
8. Termination
You may stop using the service at any time by revoking your API keys. Closing an account today is a manual process — email [email protected] to request it. We may suspend or terminate your access for breach of these terms, including non-payment.
9. Changes to these terms
We'll update this page when the terms change, and update the version number and generation date at the top. Continued use of the API after a change takes effect is acceptance of the updated terms.
10. Governing law
These terms are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction over any dispute arising from them.
Contact
Questions about these terms: [email protected].