The Events API provides a queryable log of all state-change events that occur in your workspace. Each event records what changed, when it changed, and which user or robot triggered the change.
Events are immutable records of changes to workspace data. They are created automatically by the API whenever a resource is created, updated, archived, restored, or deleted. Events cannot be created, modified, or deleted via the API.
The event log retains events for 90 days on the Starter plan, 365 days on Growth, and indefinitely on Enterprise. Events older than the retention window are permanently removed.
GET/eventsList eventsViewer+▶
GET/events/{id}Get an eventViewer+▶
POST/events/filterFilter eventsViewer+▶
POST/events/countCount eventsViewer+▶
Event Types
Every event has an event_type string in the format resource.action. The table below lists all event types emitted by the Ptolemy API.
Event type
Triggered when
instrument.created
A new instrument is created
instrument.updated
An instrument is updated (name, identifier, or field values)
instrument.archived
An instrument is soft-deleted
instrument.restored
An archived instrument is restored
instrument.deleted
An instrument is hard-deleted
market.created
A new market is created
market.updated
A market is updated
market.archived
A market is soft-deleted
market.restored
An archived market is restored
market_listing.created
A new listing is created
market_listing.updated
A listing is updated
market_listing.archived
A listing is archived
market_listing_suspension.created
A trading suspension is created
market_listing_suspension.updated
A suspension is updated
market_listing_suspension.deleted
A suspension is deleted
time_series_value.created
A scalar time series value is recorded
time_series_value.updated
A scalar value is updated
time_series_value.archived
A scalar value is archived
composite_time_series_value.created
A composite time series value is recorded
webhook.created
webhook.updated, webhook.deleted
membership.created
membership.updated, membership.deleted
Delivery Log
Every webhook delivery attempt is recorded as a delivery log entry. Use these endpoints to inspect delivery outcomes and debug failed webhooks.