Skip to main content
The Ark Email API is organized around REST. It uses standard HTTP methods, returns JSON responses, and uses conventional HTTP response codes.

​
Resource Hierarchy

Ark’s API is organized around a Platform → Tenant → Domain → Email hierarchy. If you’re building a white-label email platform, most resources support a tenant_id parameter to scope operations to a specific customer:
ResourceDescriptionTenant-scoped?
EmailsSend and track transactional emails✅ Optional
TenantsManage your customers on the platformN/A (top-level)
DomainsConfigure sending domains with DNS verification✅ Optional
SuppressionsManage bounce and complaint suppression lists✅ Optional
WebhooksReal-time event notifications✅ Optional
CredentialsAPI keys for authentication✅ Optional
TrackingOpen and click tracking domains✅ Optional
Not using tenants? No problem. All tenant_id parameters are optional. If omitted, operations apply at the platform level. See Architecture Overview for when tenants are useful.

​
Authentication

All API requests require authentication via Bearer token: 
Authorization: Bearer ark_live_xxxxxxxxxxxxxxxxxxxx
See Authentication for details on obtaining and using API keys.

​
Request Format

Send request bodies as JSON with the Content-Type: application/json header: 
curl -X POST https://api.arkhq.io/v1/emails \
  -H "Authorization: Bearer $ARK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "hello@example.com", "to": "user@example.com", "subject": "Hello"}'

​
Response Format

​
HTTP Status Codes

StatusDescription
200Success
201Resource created
400Bad request - check your request body
401Unauthorized - invalid or missing API key
403Forbidden - insufficient permissions
404Resource not found
429Rate limit exceeded
500Server error

​
Rate Limiting

See Rate Limits for detailed information.

​
Pagination

List endpoints return paginated results using page-number pagination: 
{
  "data": [...],
  "page": 1,
  "perPage": 30,
  "total": 150,
  "totalPages": 5,
  "meta": {
    "requestId": "req_abc123"
  }
}
Use page and perPage query parameters to navigate: 
# First page (default)
curl "https://api.arkhq.io/v1/emails" \
  -H "Authorization: Bearer $ARK_API_KEY"

# Second page with 50 items per page
curl "https://api.arkhq.io/v1/emails?page=2&perPage=50" \
  -H "Authorization: Bearer $ARK_API_KEY"
ParameterTypeDefaultDescription
pageinteger1Page number (1-indexed)
perPageinteger30Items per page (max 100)

​
Idempotency

For safe retries on network errors, include an Idempotency-Key header on POST requests: 
curl -X POST https://api.arkhq.io/v1/emails \
  -H "Authorization: Bearer $ARK_API_KEY" \
  -H "Idempotency-Key: unique-request-id-123" \
  -H "Content-Type: application/json" \
  -d '{"from": "hello@example.com", "to": "user@example.com", "subject": "Hello"}'
Keys are valid for 24 hours. Repeating a request with the same key returns the original response.

​
API Resources

Emails

Send and manage transactional emails

Tenants

Create and manage white-label customers

Domains

Configure sending domains with DNS verification

Suppressions

Manage bounce and complaint suppression lists

Webhooks

Configure real-time event notifications

Tracking

Manage open and click tracking domains

​
Error Codes

For complete error handling guidance, see Errors.