DEVELOPERS

Straightforward integration. Serious operational behavior.

Use API keys and explicit request payloads while Cessy handles document lifecycle, render isolation, quotas, history and production evidence behind the interface.

Clear errors

Machine-readable failures make retries and customer-facing handling predictable.

Lifecycle visibility

Jobs, documents, versions and production routing remain traceable after the API call returns.

Automation ready

Schedules, batch jobs and webhooks support repeatable workflows without custom glue everywhere.

Revocable credentials

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
  }'

Illustrative request shape. Final endpoint and entitlement behavior depend on deployment configuration.

JSON RESPONSE

Example response

{
  "id": "rnd_8FJ3K2",
  "status": "completed",
  "render_ms": 1184,
  "size_bytes": 319488,
  "download_url": "https://…",
  "expires_at": "2026-10-06T21:45:00Z"
}

Talk to us about integration

FROM REQUEST TO OUTPUT

A predictable API lifecycle.

Clear authentication, input validation, isolated render execution and traceable output handling make integration easier to maintain.

Authenticate

Send a revocable API key and identify the client workflow.

Submit

Pass URL or HTML with explicit page settings.

Render

Work is processed behind isolated workers and limits.

Retrieve

Receive status, metadata and a temporary output link.