Skip to main content
Version: 2019-05-29 (Current)

Retrieve an event

Retrieve detailed information about a specific event. Use this endpoint to inspect event details, debug webhook deliveries, and verify what data was sent to your webhooks.


๐Ÿ”‘API Credentials

Request Parametersโ€‹

Required - 1 fieldPath Parameters
โ–ผ
`id`STRING(required)
The event ID to retrieve. Event IDs start with evnt_ followed by test_ for test mode.
Example:"evnt_test_5xuy4w91xqz7d1w9u0t"

Responsesโ€‹

200

Successful retrieval

Returns the event object with complete details including the data that triggered the event and webhook delivery information.

Event object includes:
  • id - Event identifier (evnt_*)
  • key - Event type (e.g., charge.complete)
  • data - Complete object that triggered the event
  • webhook_deliveries - Array of webhook delivery attempts with status and response
  • created_at - When the event occurred (ISO 8601)

401

Unauthorized

Authentication failed. Invalid or missing API key.

Common causes:
  • Missing Authorization header
  • Invalid secret key
  • Using public key instead of secret key
  • Incorrect HTTP Basic Auth format

404

Not found

Event not found or does not exist.

Common causes:
  • Invalid event ID
  • Event ID from different account
  • Mixing test and live mode keys
  • Event was created more than 90 days ago (events are retained for 90 days)

Code samplesโ€‹

curl https://api.omise.co/events/evnt_test_5xuy4w91xqz7d1w9u0t \
-u skey_test_5xuy4w91xqz7d1w9u0t:

Error and result codesโ€‹

Common Error Codesโ€‹

CodeDescriptionResolution
authentication_failureInvalid API keyVerify your secret key is correct
not_foundEvent not foundCheck event ID and ensure correct mode (test/live)

Webhook Delivery Status Codesโ€‹

StatusDescription
200Successfully delivered and processed
4xxClient error (bad request, authentication failure)
5xxServer error (your endpoint had an error)
nullDelivery failed (timeout, connection refused)

Try it outโ€‹

Required - 1 fields
โ–ผ