01
Clear errors
Machine-readable failures make retries and customer-facing handling predictable.
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.
POST /v1/documents/render
curl -X POST https://api.cessy.net/v1/render \
-H "Authorization: Bearer $CESSY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"source": { "url": "https://example.com/report" },
"format": "A4",
"environment": "production"
}'curl -X POST https://api.cessy.net/v1/render \
-H "Authorization: Bearer $CESSY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"source": { "html": "<main>...</main>" },
"format": "Letter",
"printBackground": true
}'DEVELOPERS
Straightforward integration. Serious operational behavior.
Illustrative request shape. Final endpoint and entitlement behavior depend on deployment configuration.
02
Lifecycle visibility
Jobs, documents, versions and production routing remain traceable after the API call returns.
03
Automation ready
Schedules, batch jobs and webhooks support repeatable workflows without custom glue everywhere.
04
Revocable credentials
API keys can be managed independently instead of sharing user passwords with applications.
API / DOCUMENT LIFECYCLE
From authoring to live evidence.
API Keys
API keys can be managed independently instead of sharing user passwords with applications.
Quick PDF
Render HTML or approved URL content with controlled page options and production-minded defaults.
Webhooks
Connect lifecycle events to downstream systems with explicit operational history.
Activity & Documents
Jobs, documents, versions and production routing remain traceable after the API call returns.
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.