API Terms

The Clapleads Atlas API lets you do programmatically what you can do in the app: search the database, manage your workspace, and export records. It uses the same account, the same plan, and the same credits as the app, and these terms add API-specific rules on top of the Terms of Use.

• API keys belong to your user account. You are responsible for everything done with your keys.
• A key is shown once when you create it. We store only a secure hash, so we cannot show it again — if you lose it, create a new one.
• Keep keys secret. Do not put them in client-side code, public repositories, or shared documents.
• You can revoke a key at any time. Revoke immediately if you think a key has leaked, and tell us through the support page.

Current limits per account:

Requests over a limit get an HTTP 429 response — back off and retry later. We may change limits to keep the service healthy; if we lower them in a way that matters, we will say so in the changelog or release notes.

Exporting records through the API spends credits exactly like exporting in the app: 1 credit per record, from the same monthly balance. See Billing, Renewals & Refunds for how credits work.

You may not:

• evade rate limits or credit accounting — for example by rotating keys, spreading requests across multiple accounts, or exploiting bugs;
• use the API to scrape or mirror the database beyond the export features and limits of your plan;
• reverse engineer the service or probe it for vulnerabilities without written permission (see the Acceptable Use Policy);
• misrepresent your application or who is making requests.

API access and the data it returns are for your own business use. You may build internal tools and integrations on it, but you may not resell API access, sublicense the data, or use the API to power a competing data product. Exported records carry the same license as app exports.

We may throttle, suspend, or revoke API access — for a key or a whole account — if it breaks these terms, threatens the stability of the service, or shows signs of abuse. For serious abuse we may act immediately and explain afterwards. Where reasonable, we warn first.

The API will evolve. We may add, change, or retire endpoints. We try to avoid breaking changes, and when they are unavoidable we aim to give notice in advance through the app or release notes.

These API Terms are part of the Terms of Use. The Acceptable Use Policy and Privacy Policy apply to API use the same way they apply to the app. If these API Terms conflict with the Terms of Use about the API, these terms win.