API Terms

1. Scope

1.1 These API Terms form part of our Terms and Conditions and apply whenever you use our API, including the plan API included with some subscriptions, the data API plans and the email verification API. The Data Sharing Terms apply to the data you receive. Where we agree a separate written reseller or enterprise agreement with you, that agreement takes priority.

2. Access and keys

2.1 API keys belong to your account and are shown once, when you create them; we store only a secure hash. Keep them secret, do not embed them in public code, browser applications or mobile apps, and revoke any key you think has leaked. You are responsible for all use of your keys. Creating a key requires the API confirmation in your dashboard.

3. Automated and AI agent access

3.1 The section of the Terms and Conditions on automated and AI agent access applies to every agent key, every connection made through our MCP server and every automated client of the API. You are responsible for your agents and for all use of their keys and connections.

3.2 Agent keys and connections carry the caps you set (monthly Credits, monthly verification credits, daily calls and an approval threshold). Paid actions need a confirmation step and, above your threshold, your own approval in the dashboard. On the API an agent key receives contact details only for records your account already owns, and it cannot start verification jobs outside the confirmation step.

3.3 Records obtained by an agent may be shown or passed to anyone outside your business only where your data API plan licenses resale, and then only on the terms of that licence. The licence by plan below applies to agents in the same way as to any other client.

3.4 A paid or sending tool works in two calls: the first returns the price or a summary and a confirmation token that expires after a few minutes, and only a second call with that token carries out the action. Show the summary to the person who will approve it before you send the token. Outreach batches also wait for the account holder’s own review and approval in the dashboard.

4. Plans, allowances and rate limits

4.1 Each plan has a rate limit, a daily call limit and, for data API plans, a monthly record allowance, all shown on the API access page and in your dashboard. Requests over a limit are refused. Usage is reported for each key.

4.2 Records beyond a data API plan’s monthly allowance are billed at the overage rate shown for the plan, for each started 1,000 records, or are refused where the plan has a fixed cap. Email verification through the API is charged at the rate shown for your plan, and unknown results are free.

4.3 You must not try to evade limits, for example by spreading requests across several accounts or keys. Repeated attempts may lead to suspension.

5. Licence by plan

5.1 Plan API access included with subscriptions and the Developer data API plan are for internal use only: you may use the records inside your own business as allowed by the Terms and Conditions, but not display them to anyone outside it.

5.2 The Embed and Volume data API plans (called Starter and Growth before 2 November 2026; the rights are unchanged) may display and deliver records to your own end customers as part of your own product. Licence plan terms are agreed by contract. On every plan you may not sell, rent or pass on records as raw lists or files outside your product, resell the database as a standalone product, or use the data to build a competing database.

5.3 Contact details are returned only for records your account owns or that your plan entitles you to receive.

6. Your end customers

6.1 Where your plan allows you to display records in your product, you remain a controller of the data you receive and are responsible for your end customers’ use of it. Your terms with them must require them to comply with UK GDPR and PECR (including consent before marketing emails to sole traders and partnerships where the law requires it), forbid resale and consumer targeting, and pass on suppression and opt-out requests. You must stop supplying any end customer who breaches those terms.

7. Caching, freshness and deletion

7.1 You may cache records for at most 90 days, after which you must refresh them through the API or delete them. When your plan or agreement ends, you must delete all records obtained through the API within 30 days, unless the law requires you to keep them, and confirm the deletion in writing if we ask.

8. Suppression and opt-out requests

8.1 When a business is removed or suppressed we stop returning it. You must delete or suppress any record we report as removed or suppressed, through the API or by email, promptly and in any case within 7 days, and pass the request on to any end customer who received the record.

9. Prohibited use

9.1 You must not: rebuild, mirror or scrape our database through the API; share keys or give others access to them; resell raw data; use the data for consumer marketing, harassment, discrimination or any unlawful purpose; use the data to train a model offered to third parties; combine records with special category data; present our scores as public ratings or reviews of a business; remove AI labels, source dates or notices; or interfere with or overload the API.

10. Presentation of data

10.1 If you display records in your product, you must not misrepresent their source or freshness, must show the date a record was last checked where you show contact details, and must describe our scores as indicators for comparing leads, not ratings or guarantees. You must not use our name or logo except as we agree in writing.

11. Security and monitoring

11.1 You must keep data received through the API secure. We monitor API use for security, billing and compliance with these terms, and may ask you for reasonable information about how you use and protect the data.

11.2 Responses carry a reference that identifies the day and, by a one-way hash, the client that received them, so that we can trace copies made in breach of these terms. It is a label, never a false value. You must not remove or alter it from copies you keep or, where your plan allows, pass on.

12. Changes and availability

12.1 We may change or retire endpoints and fields. Where a change is not backwards compatible, we will give reasonable notice where practical, usually at least 30 days, except where a change is needed for security, legal or data protection reasons. The API is provided on an as is and as available basis, without a service level unless we agree one in writing.

13. Suspension and termination

13.1 We may suspend or revoke keys immediately if we reasonably believe they have been compromised, are being used in breach of these terms or the licence, or create a security or legal risk. Termination of your plan or account ends your access to the API. The sections on caching, deletion, suppression and prohibited use continue after termination.

14. Liability

14.1 The limits and exclusions of liability in the Terms and Conditions apply to the API. In particular, for business customers our total liability arising out of or in connection with the API is limited to the greater of £100 and the total fees you paid us in the 12 months before the event giving rise to the claim, and nothing limits liability for death or personal injury caused by negligence, for fraud or for anything else that cannot be limited by law.

14.2 Your indemnity in the Terms and Conditions covers your use of data received through the API and your end customers’ use of it.