Authentication

All Sent 24/7 API requests authenticate with a Bearer token in the Authorization header. The platform issues two kinds of keys:

Key prefix	Scope	What it can do
sk_live_…	Seller (lead source)	Submit leads via /api/v1/leads and /api/v1/leads/ping
pk_live_…	Buyer (lead recipient)	Report dispositions and rejections via /api/v1/postback/*

Authorization: Bearer sk_live_8f3c…

Getting a key

Keys are minted by the tenant’s admin from the dashboard:

• Seller keys — Suppliers section → pick a supplier → Regenerate under API Configuration.
• Buyer postback keys — Buyers section → pick a buyer → Portal tab → Generate key.

Caution

The plaintext value is shown once at generation time. The platform only stores its SHA-256 hash, so a lost key cannot be recovered — only revoked and replaced. Regenerating a key revokes the previous one immediately.

Base URL

https://api.sent247.com

Rate limits

Each key gets a per-second + per-day budget. Exceeding it returns:

HTTP/1.1 429 Too Many Requests
Retry-After: 30

Back off, then retry with the same Idempotency-Key (see the Postback reference).

Errors

Every error response is JSON with the same envelope:

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Rejection reason not allowed by policy",
    "details": []
  }
}

HTTP	Code	When
400	VALIDATION_ERROR	Bad JSON, missing required field
401	INVALID_API_KEY	Missing or revoked Authorization
403	—	Right key, wrong scope (e.g. seller key on a buyer endpoint)
404	—	Resource not found, or not owned by your tenant/buyer
409	DUPLICATE_LEAD	Idempotency collision with a different body
422	VALIDATION_ERROR	Policy / pipeline rejection (see endpoint pages)
429	RATE_LIMITED	Over your key’s rate limit