Integration Details

Every time you mark an article as ready, we will POST its structured content to your webhook. The request uses JSON with the fields described throughout this guide, and retries are handled by your own infrastructure.

The call originates from our cloud workers in the same region as your workspace. You can allowlist our bearer token or layer on IP restrictions if you have that control. Treat the token like any other secret-keep it out of client bundles and rotate it whenever someone leaves your team.

Log every request body before processing and build idempotency by checking the slug field. Some teams keep a hash of the payload; if the same slug + hash combination arrives twice, you can return 200 immediately to avoid duplicates.

Adopt a lightweight retry strategy as well. A common pattern is to enqueue the payload (Redis, SQS, RabbitMQ) and respond with 200 right away. Your worker can then fan-out to multiple services, apply transformations, and handle temporary CMS outages. If you need to signal an error, return a 4xx/5xx and alert your team through your monitoring stack.