Clear errors
Machine-readable failures make retries and customer-facing handling predictable.
API key e payload chiari all’esterno; lifecycle, isolamento, quote ed evidenza all’interno.
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
}'
Illustrative request shape. Final endpoint and entitlement behavior depend on deployment configuration.
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.
API keys can be managed independently instead of sharing user passwords with applications.
Render HTML or approved URL content with controlled page options and production-minded defaults.
Connect lifecycle events to downstream systems with explicit operational history.
Jobs, documents, versions and production routing remain traceable after the API call returns.
API key e payload chiari all’esterno; lifecycle, isolamento, quote ed evidenza all’interno.