Events occur when resources change state. Therefore, they become significant triggers in your account for decisions and actions. When an event occurs, we create a new event object. The event object has a structured template with an
ID, and related Speed resource nested under
You can use APIs to retrieve an individual event or a list of events occurring in your account. Once you have the event object, check the
event_type to know which event happened. To know more about the type of events we provide, check this out.
Event data is rendered according to the Speed version at its creation time, specified in the event object's api_version attribute. You will see event data in the Speed web application retained for 30 days. After that, the data is archived or deleted.
Let's see how events are logged now that you know what they are. The following table describes how Speed logs events for your account.
|APP||When your actions or your user’s actions on the Speed app or web app result in Speed resource modification.||Logs one or more events on the events page.|
|API||When you manually call an API.||Logs one or more events on the events page.|
|Automatic||When any speed resource gets modified due to Speed system generated action or an on-chain payment process.||Logs one or more events on the events page.|
We also have webhooks for sending the Event objects directly to an endpoint on your server. Our Webhooks guide will help you get set up.
Updated about 2 months ago