Skip to main content
The Sentvia API gives you full programmatic control over email infrastructure for your AI agents — create and manage inboxes, send and receive messages, and query threads, all through a RESTful interface that returns JSON and uses standard HTTP status codes.

​
Base URL

Every request is made against the following base URL. All endpoints shown in this reference are relative to it. 
https://sentvia-api-production.up.railway.app/v1

​
Authentication

The Sentvia API uses Bearer token authentication. Include your API key in the Authorization header of every request. 
curl https://sentvia-api-production.up.railway.app/v1/inboxes \
  -H "Authorization: Bearer sv_live_…"
You can create and revoke API keys at any time from the Sentvia Console. Keys are prefixed with sv_live_ for production environments. See Authentication for full details on key scopes and rotation.
Keep your API key secret. Do not commit it to source control or expose it in client-side code. Rotate it immediately in the Console if it is ever compromised.

​
Conventions

All requests and responses follow a consistent set of conventions across every endpoint.
  • JSON everywhere — set Content-Type: application/json on requests with a body; all responses are JSON-encoded.
  • IDs are opaque strings — treat them as black boxes. Do not attempt to parse structure or order out of them.
  • Timestamps are ISO-8601 UTC — for example, 2024-11-01T09:30:00Z. Always store and compare them in UTC.
  • Errors use {"error": "…"} — every non-2xx response includes a JSON body with a machine-readable error code and an optional human-readable message field. See Error handling.
  • Idempotency via client_id — when sending messages, pass a unique client_id string to make retries safe. The API deduplicates requests that share the same client_id within a 24-hour window.
Every endpoint page in this reference includes a Try it panel. Open it, paste your API key, and call the live API directly from your browser — no extra tooling required.