The CECO PDF API: correct text in PDFs from your own systems

Correct text in PDFs from your own systems, and get back proof of what changed: the same corrections, verification and record as the CECO interface, over HTTPS, with an API key.

An API key belongs to a Business account. Every route on these pages accepts one, and no other route does: a key corrects documents and reads the record of what it did. It cannot buy anything, change the account, sign anybody in or mint more keys.

• Quickstart: from a key to a corrected, verified PDF in five minutes.
• Authentication: the key format, storing keys, rotating them, and when a key stops working.
• Endpoint reference: every route a key can call, generated from the same list the service enforces.
• Errors: every error code, what it means, and what to do.
• Limits: sizes and pages per plan, rate limits and their headers.
• The verification model: what "verified" means, and how to check it yourself.
• Examples: curl, Python and Node.
• Changelog: what changed, and the versioning promise.

The machine-readable schema is at /docs/api/openapi.json. It lists only the routes a key can call.