canonical: https://jentic.com/apis/debounce.io/debounce # DeBounce API DeBounce is an email verification and validation service whose v1 API exposes five focused endpoints for checking deliverability, detecting disposable addresses, looking up reverse profile data, and reading account balance. Authentication is a single API key passed as the api_key query parameter. The API is designed for both per-address checks and bulk verification when paired with DeBounce's upload-based workflow, and the lightweight surface makes it straightforward to wire into form submission handlers and outbound email pipelines. ## For AI agents Verify whether an email address is deliverable, risky, or disposable, and look up associated profile data via DeBounce's five-endpoint validation API. ## Scope Does not handle email sending, inbox placement testing, or SMTP-time verification - use for DeBounce email validation and reverse lookup only. ## Capabilities - Validate a single email address for deliverability and risk classification at the root /v1 endpoint - Detect disposable email addresses via /disposable - Reverse-lookup a profile by email through /append (Data Append) - Retrieve a company logo for a given email domain at /logo - Read the remaining DeBounce credit balance with /balance ## Use cases ### Inline signup form email validation Web forms that capture email addresses can call DeBounce's root /v1 endpoint with the supplied address and reject submissions that come back as undeliverable, risky, or part of a catch-all domain. Because the call is a single GET with the api_key query parameter, it can run from a form-handler edge function in milliseconds. Pairing it with /disposable as a fast-path filter keeps throwaway addresses out of the database before they ever reach the verifier. Example prompt: GET /v1?email={email} and reject the submission if the response status is not 'deliverable' or the role/disposable flags are true. ### Outbound campaign list hygiene Marketing teams running cold-email or transactional campaigns need to clean lists before they hit a sending platform. DeBounce's per-email check classifies each address as deliverable, risky, disposable, or unknown, and the /balance endpoint lets a workflow halt before exhausting credits. Used in batch, this prevents bounce-rate spikes that hurt sender reputation on downstream platforms. Example prompt: Loop the inbound list, call GET /v1?email={email} per address, and write only addresses with status='deliverable' to the campaign segment. ### Reverse profile lookup for sales prospecting Sales workflows that have an email address but no other context can call /append to retrieve associated profile data, then use /logo to enrich the record with the prospect's company logo for visual context in a CRM. Together these two endpoints turn a bare email into a usable lead row without touching a separate enrichment provider. Example prompt: GET /append?email={email} for profile data, then GET /logo?domain={domain} and store both on the CRM contact record. ### AI agent verifying emails through Jentic An agent processing inbound leads can search Jentic for 'verify an email address' and execute DeBounce's check without ever holding the api_key. The agent receives a clean classification it can branch on - deliverable, risky, or disposable - and can also pull /balance to decide whether to keep verifying or escalate to a human to top up credits. Example prompt: Search Jentic for 'verify an email address', execute /v1 with the email, and route deliverable results to the CRM and disposable results to a quarantine queue. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/` | Validate a single email address | | GET | `/balance` | Get remaining credit balance | | GET | `/disposable` | Detect disposable email | | GET | `/append` | Reverse email lookup (Data Append) | | GET | `/logo` | Get company logo for a domain | ## Key resources - **Validation** — Single-address email deliverability check and disposable detection - **Data Append** — Reverse profile lookup and company logo retrieval - **Account** — Remaining credit balance ## Why Jentic - **Setup:** Wiring the DeBounce API by hand means learning its root-path validation convention and passing the api_key as a query parameter across the validation, balance, and disposable endpoints. Through Jentic you install once, import the DeBounce API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** DeBounce carries the email address in the request parameters rather than as a resource id in the URL path, so limit the agent to the operations it needs, such as validating an email or checking whether it is disposable. Every operation here is a read-only GET, so no sending or write path is reachable. - **Credential handling:** Your DeBounce api_key is stored once, encrypted, by your own Jentic One instance and appended as a query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'verify an email address' or 'check disposable email', and Jentic returns the matching DeBounce operation with its input schema so the agent calls the right endpoint without remembering the root-path validation convention. ## Related APIs - **Hunter API** — Email finder and verifier with domain-search prospecting features. - **Kickbox API** — Email verification with deliverability scoring and ESP integrations. - **NeverBounce API** — Real-time and bulk email verification with auto-cleaning of bad addresses. - **Clearbit API** — Person and company enrichment beyond what /append returns. ## FAQ ### What authentication does the DeBounce API use? DeBounce uses an API key passed as the api_key query parameter on every request. Through Jentic the key is held in the encrypted vault and added to each call at execution time, so the raw key never enters the agent's prompt or response. ### Can DeBounce detect disposable email addresses? Yes. GET /disposable returns whether an address belongs to a known disposable or temporary provider, separate from the full deliverability check at the root /v1 endpoint. Use it as a fast-path filter before spending credits on the deeper validation. ### How do I check my DeBounce credit balance through the API? GET /balance returns the remaining credits on the account. Run it before a large batch to avoid mid-run failures, and treat a low balance as a trigger to alert a human rather than silently halting the workflow. ### What are the rate limits for the DeBounce API? The OpenAPI spec does not document explicit rate limits. For high-volume list cleaning, DeBounce recommends the upload-based bulk workflow rather than per-address GETs - the synchronous API in this spec is best suited for inline signup-form validation. ### How do I validate an email address through Jentic? Run pip install jentic, search for 'verify an email address', and Jentic returns the DeBounce /v1 operation with its input schema. Load it, supply the email, and execute. Branch on the returned status field - 'deliverable', 'risky', 'disposable', or 'unknown'. ### Does DeBounce verify emails in real time during the SMTP handshake? The spec exposes synchronous GET endpoints rather than SMTP-time hooks. Treat the API as a pre-send or pre-store filter: validate at form submission or before list import rather than during message transmission. ### Can I limit what my agent is allowed to do with the DeBounce API? Yes. Because you run Jentic One yourself, your own rules decide which DeBounce operations your agent may call, so you can grant just the ones it needs, such as validating an email at the root /v1 endpoint or checking /disposable, while withholding /append, /logo, or /balance. Every DeBounce operation is a read-only GET that carries the email in the request parameters rather than as a resource id in the path, so no sending or write path is ever reachable. Your API key is stored by your own instance and added at execution time, so the agent never sees the raw credential.