DeBounce API

Name: DeBounce API API
Brand: DeBounce API
Availability: InStock

✓ Official Vendor SpecData EnrichmentContact EnrichmentapiKey5 EndpointsREST

For Agents

Verify whether an email address is deliverable, risky, or disposable, and look up associated profile data via DeBounce's five-endpoint validation API.

Quickstart

Get started with DeBounce API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"verify an email address"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DeBounce API API.

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

GET STARTED

Start building with DeBounce API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DeBounce API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

5 endpoints — 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.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The DeBounce api_key is stored encrypted in the Jentic vault (MAXsystem). Agents execute operations through Jentic and the key is appended to the request as a query parameter at call time — it never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'verify an email address' or 'check disposable email') and receive the matching DeBounce endpoint with its input schema, with no need to remember the root-path validation convention.

Time to first call

Direct DeBounce integration: a few hours for key handling and the per-endpoint request shapes. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hunter API

Email finder and verifier with domain-search prospecting features.

Choose Hunter when you also need to discover emails for a domain, not just verify ones you already have.

Alternative

Kickbox API

Email verification with deliverability scoring and ESP integrations.

Choose Kickbox when you want a richer per-address quality score and tighter integration with sending platforms.

Alternative

NeverBounce API

Real-time and bulk email verification with auto-cleaning of bad addresses.

Choose NeverBounce when you want auto-cleaning of imported lists rather than per-address verification only.

Complementary

Clearbit API

Person and company enrichment beyond what /append returns.

Pair with DeBounce when you need richer firmographic enrichment after confirming an email is real.

FAQs

Specific to using DeBounce API API through Jentic.

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.