Skip to content
Event stream/
Get Events

Get Events

Request

Stream payment events such as payment status or quote responses

Security
bearerAuth
Headers
last-event-idstring or null(Last-Event-Id)
Any of:

SSE Last-Event-ID: the UUID7 id of the last event the client received. On reconnect, streaming resumes from that event's timestamp (browser EventSource sends this automatically). Replay is best-effort — only events still retained in the stream can be re-delivered, and same-millisecond events may be re-sent, so treat the SSE id as an idempotency key.

string (uuid)
curl -i -X GET \
  https://docs.leanx.me/_mock/openapi/v3/events \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'last-event-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'

Responses

Server-sent event stream (text/event-stream). Each event carries an event name, a UUID7 id (echo it back via Last-Event-ID to resume), and a data line holding JSON: a PaymentResponse for payment events and a PaymentError for payment-error events.

Bodytext/event-stream
datastring
eventstring

Event type / data payload variant

Enum:"payment""payment-error"
idstring, (uuid)

UUID7 event id (SSE Last-Event-ID cursor)

retryinteger, >= 0
Response
event: payment
data: {"id":"019f8da0-591c-771e-b353-cdc75173dccc","external_id":"29fc8b3dc79442c3","timestamp":"2026-07-23T06:18:43.873162Z","status":"queued","msg":"Queued","quote":"019f8da0-58d4-760a-8dcf-4a221003a022"}
id: 019f8da0-6a1b-7c4e-8f21-0a1b2c3d4e5f