Skip to main content
A webhook tells your own code when something happens in a project, so it can act without polling the API. ChatFeatured sends each event as a signed POST to the URL you choose, and retries for up to 72 hours when your URL doesn’t answer. Find them under Integrations → Webhooks, in the Developer section. Each project has its own endpoints, up to 20. Owners and admins can also add organization endpoints, which get every project’s events at one URL. Viewers can see endpoints and deliveries but can’t change them.
These webhooks are separate from the older ones on the Project REST API (v1) page. They’re signed differently, so follow this page for endpoints you add under Integrations → Webhooks.

Add an endpoint

1

Open Webhooks

Go to Integrations → Webhooks and click Add endpoint.
2

Enter the URL

Your receiver’s address, such as https://example.com/webhooks/chatfeatured. It must be a public https URL with a hostname, not an IP address. Add a Description if you’ll have several endpoints.
3

Pick the events

Choose All events, including new kinds we add later, or Only the events I pick and tick the groups you want.
4

Copy the signing secret

Click Add endpoint. The signing secret (it starts with whsec_) shows once. Copy it into your receiver’s settings before you click Done. You can’t see it again, only rotate it.
5

Send a test

Open the endpoint and click Send test event. A webhook.test event goes out, and the delivery shows up under Deliveries with your receiver’s response.

Organization endpoints

An organization endpoint gets the events of every project in your organization, including projects you add later, at one URL. An agency can point one endpoint at all its clients instead of adding one per project. It also gets events that belong to the organization rather than a project, such as AEO reports. Only owners and admins see them. On any project’s Integrations → Webhooks page, find Organization endpoints and click Add endpoint, then follow the same steps as above. An organization can have up to 20. Each delivery says which project it came from in data.projectId. To get only report events, pick AEO reports and Performance reports under Only the events I pick.

Events

Each group covers every event that starts with its prefix, such as article. for Articles, including kinds added later. Work that takes a while, such as writing an article or running a site audit, runs as a job. When a job ends it sends job.succeeded, job.failed or job.canceled, with the kind of work in data.jobType and what it worked on in data.resource. Writing an article also sends article.generation.started when it begins, then article.generation.succeeded, article.generation.failed or article.generation.canceled. A performance report or AEO report sends .completed or .failed when it finishes, whether it was started from the dashboard, the API or your AI agent.

What a delivery looks like

Every delivery is a POST with a JSON body:
data.object names what the event is about, and data.projectId the project it happened in, when there is one. Some events add a few details next to it. The body stays small on purpose, so fetch the full record through the API if you need it. Your receiver should answer with any 2xx status within 15 seconds. Anything else, including a redirect, counts as a failure.

Verify the signature

Each delivery carries three headers, following the Standard Webhooks spec: The HMAC key is the part of your secret after whsec_, decoded from base64. Check the signature over the raw body, before you parse the JSON, and reject timestamps more than 5 minutes old.
Any Standard Webhooks library does the same check, so you can use one instead of this code.

Retries and failing endpoints

A delivery that fails is tried again after 5 seconds, then 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours, 14 hours and twice more after 20 hours each. That’s 10 attempts over about 72 hours, after which the delivery shows as Failed. While deliveries keep failing, the endpoint page says since when. If an endpoint fails for 72 hours without a single success, ChatFeatured turns it off and sends a webhook_endpoint.disabled event to your other endpoints. Fix the receiver, click Send test event to check it, then click Turn on.

Deliveries

The endpoint page lists its deliveries, newest first, with their status (Pending, Retrying, Succeeded or Failed), the response code, the attempts and the time. Click one to see the payload, your receiver’s response, the error and when the next retry goes out. Replay sends the same event again as a new delivery, which helps after you’ve fixed a bug in your receiver.

Rotate the signing secret

Open the endpoint, click Rotate secret and confirm. The new secret shows once. For the next 24 hours, deliveries carry signatures from both the old and the new secret, so you can update your receiver without missing any. After that, only the new one signs.

Change or remove an endpoint

On the endpoint page, Edit changes the URL, description and events. Turn off pauses deliveries without deleting anything, and Delete removes the endpoint and its deliveries. You can also manage endpoints through the API and the MCP server, in the webhooks area.

Troubleshooting

Webhooks only go to https URLs. Put your receiver behind TLS, or use a tunnelling tool while you develop.
ChatFeatured only sends to addresses on the public internet. A URL on your office network, localhost or a cloud-internal hostname won’t work. Use a public hostname for your receiver.
Check the signature over the raw request body, before any JSON parsing or reformatting, and decode the part of the secret after whsec_ from base64. If you rotated the secret, update your receiver within 24 hours.
Your receiver didn’t answer within 15 seconds, or the connection failed. Answer with a 2xx straight away and do slow work afterwards.
Last modified on November 17, 2026