> ## Documentation Index > Fetch the complete documentation index at: https://developers.perkstar.co.uk/llms.txt > Use this file to discover all available pages before exploring further. # List transactions ## OpenAPI ````yaml /api/openapi.yaml get /transactions openapi: 3.1.0 info: title: Perkstar Public REST API version: 2026-05-04.oauth description: | Programmatic access to your Perkstar loyalty data. Two authentication modes are supported: - **API key.** Per-org bearer token issued from Settings → API keys (`pk_live_…` / `pk_test_…`). Right choice for direct integrations, single-tenant POS adapters, and back-office sync. - **OAuth 2.0.** Three-legged authorization-code flow with PKCE, for marketplace listings (Square App Marketplace, Shopify App Store, Toast Partner Marketplace, Lightspeed). The merchant installs your app from the partner marketplace, lands on `/oauth/authorize`, approves the requested scopes, and your server exchanges the code at `/api/oauth/token` for a short-lived access token. See the dedicated OAuth section below. Every endpoint is scoped, rate-limited, and idempotent on POST. POS-adapter builders should start with the `/marketplace/*` endpoints — they collapse the typical "find-or-create customer + enrolment + post transaction" flow into a single round-trip with permanent dedupe via `external_transaction_id`. ## Test credentials Test credentials (`pk_test_…` or OAuth applications in TEST mode) can read API data, create isolated test transactions, and simulate wallet pushes. They cannot create, update, or delete live customers, enrolments, or webhook configuration. Test calls to `/marketplace/accrue` only work with an existing customer and enrolment; `/marketplace/enroll` is live-only. This prevents a sandbox integration from changing live customer records. Copy-paste cURL recipes are published at `/api/v1/curl-recipes.md` for teams that want to test the API before wiring the SDK. ## Response headers (universal) Every response, success or error, carries: - **X-Request-Id** — unique per request. Echo this in support tickets; we can find the exact call in the per-key audit log. - **X-API-Version** — date-versioned schema marker (`2026-05-04` as of writing). 12-month deprecation policy. - **X-RateLimit-Limit** — per-minute quota for the credential. - **X-RateLimit-Remaining** — tokens left in the current window. - **X-RateLimit-Reset** — unix-seconds when the window refills. - **Retry-After** — emitted on 429 only; seconds to wait. The reusable error responses below (`Unauthorized`, `Forbidden`, `NotFound`, `RateLimited`, `ValidationError`) declare these as strongly-typed `headers` so codegen against an error path has them. Success responses inline their `"200"` / `"201"` and rely on this convention rather than per-endpoint header declarations. contact: name: Perkstar url: https://perkstar.co.uk servers: - url: https://dashboard.perkstar.co.uk/api/v1 description: Production security: - bearerAuth: [] paths: /transactions: get: tags: - Transactions summary: List transactions operationId: listTransactions parameters: - $ref: '#/components/parameters/Cursor' - $ref: '#/components/parameters/Limit' - in: query name: enrollmentId schema: type: string - in: query name: customerId schema: type: string - in: query name: type schema: type: string enum: - STAMP - REDEEM - ADJUST - in: query name: mode description: | Filter by ledger mode. Default is `live` (sandbox rows are hidden). Use `test` to list only `pk_test_…`-created rows for sandbox auditing, or `all` to return both. schema: type: string enum: - live - test - all default: live - in: query name: createdAfter schema: type: string format: date-time - in: query name: createdBefore schema: type: string format: date-time responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TransactionList' security: - bearerAuth: [] components: parameters: Cursor: in: query name: cursor schema: type: string description: Opaque cursor returned in `next_cursor`. Limit: in: query name: limit schema: type: integer default: 50 minimum: 1 maximum: 200 schemas: TransactionList: allOf: - $ref: '#/components/schemas/Pagination' - type: object properties: data: type: array items: $ref: '#/components/schemas/Transaction' Pagination: type: object required: - data - has_more - next_cursor - limit properties: has_more: type: boolean next_cursor: type: string nullable: true limit: type: integer Transaction: type: object properties: id: type: string enrollment_id: type: string type: type: string enum: - STAMP - REDEEM - ADJUST source: type: string enum: - SCANNER - POS - API - ADJUST - DASHBOARD - LEGACY_IMPORT - TAP delta: type: number multipleOf: 0.01 amount_pence: type: integer nullable: true note: type: string nullable: true external_id: type: string nullable: true external_transaction_id: type: string nullable: true description: | Partner-supplied stable identifier (Toast order id, Shopify checkout id, Square payment id). When set on create via `POST /transactions` or `POST /marketplace/accrue`, the unique `(orgId, externalTransactionId)` index makes the call permanently idempotent — a redelivered upstream webhook returns the existing row at HTTP 200 instead of double-crediting. reverses_transaction_id: type: string nullable: true description: | Set on a compensating row created by `/marketplace/reverse`. Points at the original transaction this row reverses. The original is reversed at most once (enforced by a unique constraint). reason_text: type: string nullable: true description: | Operator-visible reason for a reversal ("Customer refunded the order"). Persisted on the COMPENSATING row, not the original. test_mode: type: boolean description: | True when posted via a `pk_test_…` key. Test rows still write to the ledger and still fire webhooks (so partner sandbox integrations can verify their receivers), but DO NOT update Customer / Card / Enrollment aggregates and are excluded from operator dashboard rollups. created_at: type: string format: date-time securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: pk_live_… / pk_test_… or perk_at_… ```` ## Related topics - [List customers](/api-reference/customers/list-customers.md) - [List enrollments](/api-reference/enrollments/list-enrollments.md) - [List locations](/api-reference/locations/list-locations.md) - [List webhooks](/api-reference/webhooks/list-webhooks.md) - [List cards](/api-reference/cards/list-cards.md)