Webhooks and API quickstart

SendSure supports two common developer entry points: synchronous verification through the API and asynchronous follow-up through webhooks or downstream processing.

Create an API key

Go to the integrations or API key area in the dashboard and generate a credential dedicated to the workload you are about to build.

Use separate keys for:

production traffic
staging or QA
customer-specific or environment-specific integrations

That separation makes incident response and key rotation much simpler.

Send your first request

Start with one request and verify the shape of the response before you write wrappers around it.

curl -X POST "https://api.sendsure.ai/api/verify/single" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{"email":"alice@example.com"}'

Confirm that your integration handles both high-confidence outcomes and ambiguous ones.

Webhook sanity checks

If you are consuming webhooks:

verify the signing secret
return 2xx quickly
push heavy work into a queue
log both payload IDs and timestamps

Webhook failures are usually caused by slow handlers, incorrect secrets, or endpoints that are not reachable from the public internet.

Rate-limit and retry posture

Build for graceful retries. Even if the API is healthy, your own network and downstream services will not be perfect.

What to include in a support request

If you need API help, bring:

the endpoint you called
approximate timestamp
HTTP status code
a redacted request sample
whether the issue happens in staging or production

That is usually enough for support to narrow the failure domain quickly.

Webhooks and API Quickstart