Skip to main content
Pick the events an endpoint receives when you create or edit it. Each event is sent as the data of the event envelope. You also receive a ping event when you select Send test in the console, whatever events the endpoint subscribes to.
Events are sent to the endpoints of the account that owns the resource. In a team workspace, a teammate’s change to your agent is sent to your endpoints.

Chat

Sent for POST /agents/{AgentId}/chat requests made with an API key. Messages sent from the console playground don’t trigger chat events.

chat.completed

chat.failed

Same fields as chat.completed. credits is 0: failed requests are refunded.

Agents

agent.created

agent.updated

Sent when the agent’s name, model or instructions are saved. agent.name is the new name.

agent.deleted

The agent, its knowledge and its conversations are gone by the time you receive this event.

Knowledge

source describes what was added or removed: the title of a text entry, the question of a Q&A pair, a file name, or a website URL.

source.added

Crawling a website sends one source.added event for the whole crawl, with the URL you submitted as source.

source.deleted

Billing

credits.low

Sent once when your remaining credits drop below 20% of your last top-up or monthly allowance. It’s sent again only after your credits are refilled and run low again.

Test

ping

Sent by Send test in the console. Use it to check that your endpoint is reachable and verifies signatures correctly.
New event types may be added over time. Ignore types your handler doesn’t know instead of returning an error.