Skip to main content

​
Make your first verification request

​
1. Get an API key

Create a Bounceless account, then open Settings → API keys and create a key. Copy it immediately; the dashboard shows a newly minted key once. Set the key only in your current shell. Keep it out of source control, shell history, logs, screenshots, and prompts:

​
2. Verify a controlled address

Choose the path before you automate it:
Use only an address you are authorized to test. A 200 response contains a completed result. A 202 means the bounded synchronous wait ended before the engine completed; it contains engineJobId, requestId, and a presend object with no decision and zero billed credits. The four-route GA API does not expose a single-result polling route. Record both IDs and do not automatically resubmit the address. Use the batch flow when your integration requires a retrievable asynchronous result.

​
3. Read the decision

For a completed response, integrate against the additive presend object. Older sibling fields remain during the compatibility window. Start with presend.status, then read presend.decision, presend.verdict, presend.reasons, and presend.billing.

API key safety

Store, rotate, and revoke keys.

Decision dictionary

Interpret every public decision and verdict.
The hosted playground’s handling of an entered key is verified separately before public launch. Until that browser check is complete, use the curl example from a controlled shell rather than entering a production key in the playground.