01
Clear errors
Machine-readable failures make retries and customer-facing handling predictable.
DÉVELOPPEURS
Intégration simple. Comportement opérationnel sérieux.
Des clés API et des payloads explicites côté client, avec lifecycle, isolation, quotas et preuves côté Cessy.
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
}'DÉVELOPPEURS
Intégration simple. Comportement opérationnel sérieux.
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
De la création aux preuves en production.
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.
DÉVELOPPEURS
Intégration simple. Comportement opérationnel sérieux.
Des clés API et des payloads explicites côté client, avec lifecycle, isolation, quotas et preuves côté Cessy.