Clear errors
Machine-readable failures make retries and customer-facing handling predictable.
API-ключи и понятные payload снаружи; lifecycle, изоляция, квоты и evidence внутри.
Machine-readable failures make retries and customer-facing handling predictable.
Jobs, documents, versions and production routing remain traceable after the API call returns.
Schedules, batch jobs and webhooks support repeatable workflows without custom glue everywhere.
API keys can be managed independently instead of sharing user passwords with applications.
curl -X POST https://api.example.com/v1/render \
-H "Authorization: Bearer $CESSY_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/invoice/1284",
"format": "A4",
"landscape": false,
"print_background": true
}'curl -X POST https://api.example.com/v1/render \
-H "Authorization: Bearer $CESSY_KEY" \
-H "Content-Type: application/json" \
-d '{
"html": "<h1>Invoice #1284</h1>",
"format": "A4",
"landscape": false,
"print_background": true
}'{
"id": "rnd_8FJ3K2",
"status": "completed",
"render_ms": 1184,
"size_bytes": 319488,
"download_url": "https://…",
"expires_at": "2026-10-06T21:45:00Z"
}Clear authentication, input validation, isolated render execution and traceable output handling make integration easier to maintain.
Send a revocable API key and identify the client workflow.
Pass URL or HTML with explicit page settings.
Work is processed behind isolated workers and limits.
Receive status, metadata and a temporary output link.