Upcoming deprecation of the single-event lookup endpoint

What is changing

The Get an event by ID endpoint returns one audit log event when you already know its ID. It is deprecated, and requests to it fail starting December 21, 2026.

Nothing else in the Events API changes. The other endpoints return the same event fields, so the data you read today stays available.

What to use instead

Every event returned by the single-event lookup is also returned, with the same fields, by:

• Get events (GET /v1/orgs/{orgId}/events): paginated retrieval with filtering by time range, action, actor, product and more. Use this when you need to find events matching criteria.
• Poll events (GET /v1/orgs/{orgId}/events-stream): efficient time-ordered polling for continuous ingestion. Use this to keep a copy of your organization's events in your own system. See Migrate to the event polling API.
• Audit log webhooks: the webhook payload for an event carries the same fields as the single-event lookup response, so a system that receives webhooks already has the event and does not need to fetch it again.

How to migrate

Most integrations call the single-event lookup for one of two reasons. Pick the matching path.

You look up an event you received from another endpoint or a webhook

Stop making the second call. The event returned by Get events, Poll events and webhooks is complete; there are no fields that only the single-event lookup returns.

You store event IDs and fetch the details later

Store the event itself at the time you first see it, using Poll events for ongoing ingestion or Get events for a one-off time range. If you only have an ID and need the event, call Get events with the time range in which the event occurred, request the largest page the endpoint allows, and match on the id field of the returned events:

1
2
GET /v1/orgs/{orgId}/events?from={epochMillis}&to={epochMillis}&limit=500

If the matching event is not on the first page, keep paginating until you find it: pass the meta.next value from the response as the cursor query parameter, or request the links.next URL. Narrow the time range as far as you can: limit defaults to 30 and caps at 500, and Get events is rate limited to 10 requests per minute per user and per API path, so scanning a wide range page by page hits HTTP 429 quickly.

Timeline

• Now: the endpoint is marked deprecated in the API reference and keeps working.
• December 21, 2026: requests to the endpoint fail starting on this date.

Getting help

For guidance or questions, reach out via Atlassian Developer Support or see Get help.