> ## Documentation Index > Fetch the complete documentation index at: https://help.dash.fi/llms.txt > Use this file to discover all available pages before exploring further. # Get card financial events > Get card financial events by card ID. Returned in reverse chronological order. TransactionID can be used to group different events for the same transaction. ## OpenAPI ````yaml https://api.dash.fi/v1/public/swagger/doc.json get /cards/{id}/financial-events openapi: 3.1.0 info: contact: email: support@dash.fi name: Dash.fi Support description: >- Service allows to fetch or operate on the data from the Dash.fi API. Requires API key authentication via Bearer token. Provide your API key as a Bearer token in the `Authorization` header. Example: `Authorization: Bearer YOUR_API_KEY` title: Public Dash.fi API version: '1.0' servers: - url: https://api.dash.fi/v1/public security: - BearerAuth: [] tags: - description: > Subscribe URLs to receive POSTed events as they happen in your account. Each endpoint subscribes to one or more **topics**; when a topic fires, Dash.fi delivers the event to your URL with a JSON body matching the topic's payload schema. There is no envelope — the body is the event payload directly. Event metadata (id, topic, timestamp, signature) is carried in headers. ### Topic → payload schema Topics are versioned: the format is `..v`. Breaking changes ship as a **new** topic (`.v2`) — the old version keeps delivering its existing schema until it's retired, so subscriptions are pinned and never shift schema underneath you. | Topic | Body schema | |---|---| | `card.financial_event.v1` | `CardFinancialEvent` — see `GET /cards/{id}/financial-events` in the **Card** section for the authoritative field list. | ### Delivery shape ``` POST HTTP/1.1 Content-Type: application/json X-Outpost-Event-Id: evt_abc123 X-Outpost-Topic: card.financial_event.v1 X-Outpost-Timestamp: 2026-05-05T10:00:00Z X-Outpost-Signature: v0= { ...payload matching the topic's schema... } ``` | Header | Meaning | |---|---| | `X-Outpost-Event-Id` | Stable event identifier — the same id is sent on retries. Use it to deduplicate; delivery is **at-least-once**. | | `X-Outpost-Topic` | The topic that fired this delivery. | | `X-Outpost-Timestamp` | RFC 3339 time the event was emitted. Reject deliveries where this drifts too far from your clock to mitigate replay. | | `X-Outpost-Signature` | `v0=` HMAC-SHA256 of the raw request body, keyed with your endpoint's signing secret. | ### Verifying the signature The signature is computed over the **raw request body**: ``` HMAC-SHA256(signing_secret, raw_body) ``` Encoded as hex, prefixed with `v0=`. **Use a constant-time comparison** to avoid timing attacks. `rawBody` is the unparsed request body — the exact `Buffer` or string you received over the wire, not a re-serialised JSON object. ```js import { createHmac, timingSafeEqual } from 'node:crypto'; function verify(rawBody, signatureHeader, secret) { if (!signatureHeader) return false; const expected = 'v0=' + createHmac('sha256', secret).update(rawBody).digest('hex'); // Header may carry multiple comma-separated signatures during a rotation window. return signatureHeader.split(',').some((sig) => { const got = Buffer.from(sig.trim()); const want = Buffer.from(expected); return got.length === want.length && timingSafeEqual(got, want); }); } ``` ### Secret rotation Rotating a signing secret keeps the previous secret valid for 24 hours so you can roll the new one out without dropped deliveries. During that window, the `X-Outpost-Signature` header carries comma-separated signatures (`v0=,v0=`); accept either. The new secret is shown **once** at rotation and is never retrievable later. name: Webhooks externalDocs: description: OpenAPI JSON Specification url: /v1/public/swagger/doc.json paths: /cards/{id}/financial-events: get: tags: - Card summary: Get card financial events description: >- Get card financial events by card ID. Returned in reverse chronological order. TransactionID can be used to group different events for the same transaction. parameters: - description: Card ID in: path name: id required: true schema: type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/GetCardEventsResponse' description: Card financial events '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedErrorResponse' description: Unauthorized response '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundErrorResponse' description: Not found response '500': content: application/json: schema: $ref: '#/components/schemas/InternalServerErrorResponse' description: Internal server error response security: - BearerAuth: [] components: schemas: GetCardEventsResponse: properties: data: items: $ref: '#/components/schemas/CardFinancialEvent' type: array uniqueItems: false required: - data type: object UnauthorizedErrorResponse: properties: code: example: unauthorized type: string message: example: authorization header not provided type: string required: - code type: object NotFoundErrorResponse: properties: code: example: not-found type: string message: example: resource was not found type: string required: - code type: object InternalServerErrorResponse: properties: code: example: internal-server-error type: string message: type: string required: - code type: object CardFinancialEvent: properties: amount: description: Amount. Always positive as amountDirection determines the sign example: '123.45' type: string amountDirection: $ref: '#/components/schemas/iso.AmountDirection' cardId: description: Card id example: 123e4567-e89b-12d3-a456-426614174002 format: uuid type: string category: $ref: '#/components/schemas/dto.FinancialEventCategory' createdAt: description: UTC time when the event was created example: '2021-09-01T00:00:00Z' type: string currency: description: Currency code example: USD type: string id: description: Event identifier example: 123e4567-e89b-12d3-a456-426614174001 format: uuid type: string isReversal: description: Flag determining whether the event is a reversal example: false type: boolean isSuccess: description: Flag determining whether the event is successful example: true type: boolean issues: description: >- Issues related to the event. Error indicate transaction failure where as other types are more informational. items: $ref: '#/components/schemas/dto.TransactionIssue' type: array uniqueItems: false mcc: description: Merchant category code example: '5411' type: string merchantCity: description: Merchant city example: New York type: string merchantCountry: description: Merchant country example: US type: string merchantName: description: Merchant name example: Store Name type: string merchantPostalCode: description: Merchant postal code example: '12345' type: string merchantState: description: Merchant state example: CA type: string merchantStreetAddress: description: Merchant street address example: 12 Main st type: string merchantTaxId: description: Merchant tax id example: '201665019' type: string transactionId: description: Transaction id. Used to group events for the same transaction. example: 123e4567-e89b-12d3-a456-426614174005 format: uuid type: string required: - amount - amountDirection - cardId - category - currency - id - isReversal - isSuccess - transactionId type: object iso.AmountDirection: description: >- Amount direction. `debit` reduces the card balance, `credit` is a refund. enum: - debit - credit example: debit type: string x-enum-varnames: - DebitAmount - CreditAmount dto.FinancialEventCategory: description: Category of the financial event enum: - reservation - financial example: reservation type: string x-enum-varnames: - FinancialEventCategoryReservation - FinancialEventCategoryFinancial dto.TransactionIssue: properties: origin: example: CARD type: string reason: example: ALLOWED_MCC type: string severity: example: ERROR type: string type: object securitySchemes: BearerAuth: description: >- Type "Bearer" followed by a space and your API token. Obtain your key from the Dash.fi dashboard. Example: "Bearer YOUR_API_KEY" in: header name: Authorization type: apiKey ````