Skip to main content

Base URL

ByteSend’s API is served over HTTPS. All API endpoints are prefixed with:
If you’re running a self-hosted ByteSend instance, replace https://bytesend.cloud with your instance’s base URL.

Authentication

All API endpoints (except /v1/smtp/auth) require a Bearer token in the Authorization header:
You can create API keys under Settings → API Keys. See the API Authentication guide for full details on generating and managing keys.

SMTP authentication

The SMTP relay server uses a different scheme. SMTP clients authenticate with:
  • Username: Your team’s custom SMTP username (default: bytesend)
  • Password: Your API key

Request Format

All write requests (POST, PATCH, PUT) expect a JSON body:

Response Format

Successful responses return JSON with a 2xx status code. The shape varies by endpoint.

Error Format

All errors return a consistent JSON structure:
See the Error Codes guide for detailed descriptions and handling examples.

Rate Limiting

API requests are rate-limited per team per second. Rate limit headers are included on every response: When you exceed the limit, you receive a 429 RATE_LIMITED response. See the Rate Limits guide for retry strategies.
Rate limiting is disabled on self-hosted ByteSend instances.

Pagination

List endpoints return paginated results. Use the page and limit query parameters:
Responses include pagination metadata:

Interactive Playground

Every endpoint in the API Reference has a built-in request playground. Click the Try it button on any endpoint page to send live requests directly from the docs using your API key.