Movements (Operations)
These events are emitted by the Operations API (btrz-api-operations) when a movement is created via POST /movements (tickets are moved from one manifest to another).
Events
| Action | Event name | Endpoint |
|---|---|---|
| Tickets moved to another manifest | ticket.moved | POST /movements |
| Transaction(s) updated (tickets moved) | transaction.updated | POST /movements |
| Ticket redemptions updated (unredeemed moved tickets) | ticket.redemptions.updated | POST /movements |
- ticket.moved is emitted once per moved ticket; the payload
datais the updated ticket object. - transaction.updated is emitted once per distinct transaction that had tickets moved; the payload
datacontains_id(transaction id). - ticket.redemptions.updated is emitted for each moved ticket that was unredeemed (loyalty redemption may be removed); the payload
datais the updated ticket.
Payload structure (common)
Webhook payloads include standard fields: attemptId, created, event, id, livemode, and data. For these events the handler passes providerId, apiKey, and data to the emitter.
ticket.moved — data
The data object is the updated ticket (full ticket document after the move). Type: object (ticket schema from Operations API).
transaction.updated — data
The data object contains the transaction id: { "_id": ". Type: object.
ticket.redemptions.updated — data
The data object is the updated ticket (unredeemed ticket after move). Type: object (ticket schema).
Field descriptions (payload envelope)
| Field | Type | Description |
|---|---|---|
| attemptId | string | Delivery attempt identifier. |
| created | number | Unix timestamp when the event was created. |
| event | string | Event name (ticket.moved, transaction.updated, or ticket.redemptions.updated). |
| id | string | Unique event id. |
| livemode | boolean | Whether the event is from live or test mode. |
| data | object | Event payload: updated ticket(s) or transaction id. |