API reference
Vorynza REST API base URL, authentication, and common patterns.
The Vorynza API lets you programmatically provision databases, manage mail services, handle DNS zones, and manage billing. All endpoints return JSON.
Beta
The API is under active development. Endpoints listed reflect the current surface area. Authentication tokens and interactive docs will be available with the public beta.
Base URL
https://api.vorynza.cloud/v1Authentication
Session-based (dashboard)
Dashboard API routes authenticate via your browser session. No additional headers are needed.
API key-based (programmatic)
Machine-to-machine endpoints use a Bearer token in the Authorization header:
curl https://api.vorynza.cloud/v1/mail/send \
-H "Authorization: Bearer vnz_mail_your_api_key"API keys are scoped to specific permissions per product (e.g. mail:send, dns:read).
Provider events
Provider webhooks (e.g. SES delivery events) are authenticated via HMAC signatures.
Response format
All responses follow a stable JSON shape:
{
"ok": true,
...
}Error responses include a message and optionally an error code:
{
"ok": false,
"message": "Invalid input",
"code": "validation_error"
}HTTP status codes
| Code | Meaning |
|---|---|
200 | Success |
202 | Accepted (async operation queued) |
400 | Invalid input |
401 | Authentication failure |
402 | Billing or quota error |
403 | Permission denied |
404 | Resource not found |
429 | Rate limited |
500 | Server error |
Products
- Postgres API — Provision and manage databases
- Mail API — Send email and manage mail services
- DNS API — Manage zones, records, and security gateway
Questions about the API? Contact support.
