# Events

Events are persisted throughout the lifecycle of a payment/action as you use our API. We use events to notify you when something important happens in your account (or a linked sub account). The most commonly used event occurs when a payment is captured, in which case we persist a `PaymentSession.captured` event and then (optionally) send it to any webhooks you have registered that are listening for that event type.

Note that if you are taking payments as a platform (for sub accounts), events are saved against the sub account `accountId`, but will be sent to any webhooks that your account has configured.


## Retrieves events in sorted (by epoch) order

 - [GET /events](https://developer.ryftpay.com/documentation/api/reference/openapi/events/eventgetlist.md): Retrieves a list of events. They are returned in sorted (by epoch) order (default is newest first). You can query one of your sub-account's events buy using the Account header.

## Retrieve an Event by Id

 - [GET /events/{eventId}](https://developer.ryftpay.com/documentation/api/reference/openapi/events/eventgetbyid.md): This is used to fetch an Event by its eventId