> ## Documentation Index > Fetch the complete documentation index at: https://docs.sahlfinancial.com/llms.txt > Use this file to discover all available pages before exploring further. # List the transactions of a bank connection > **Who can call it:** Any signed-in member of the workspace. Six months of generated transactions, newest first, amounts in MAD. Not paginated. **Production behaviour.** No open-banking provider is live. This route answers `409` with the code `bank_connect_unavailable` unless the request is made in the Sandbox: send `X-Sahl-Environment: sandbox` (or `?environment=sandbox`). In the Sandbox the data is simulated and derived from the connection id; it is not read from a bank. A request with no environment is also refused. **Auth:** dashboard session (`Authorization: Bearer `). Not available with a partner API key. ## OpenAPI ````yaml /openapi-console.json get /v1/bank-connections/{connection_id}/transactions openapi: 3.1.0 info: title: Sahl Console API version: 0.1.0 description: >- **Used by the Sahl console. Not available with partner API keys. Contact Sahl if you need programmatic access.** These are the routes the Sahl console calls with a signed-in user's session. They are documented so that a developer or a workspace admin can see what the console does, with the real request and response models. They are **not** part of the [Partner API](/api-reference/introduction): an API key is refused here (401), there is no try-it, and the shapes can change with the console. Authentication: `Authorization: Bearer `, the JWT the console gets from `POST /v1/auth/login` (30 minutes; renewed with `POST /v1/auth/refresh`, refresh token valid 7 days). There is no cookie. The role of the user is read from the user's record on every call, not from the token. Every call is scoped to the workspace of the user. Common answers: 401 (no or bad session), 403 `Insufficient permissions` (role), 422 (validation), 429 (100 requests per minute and IP). Error bodies have the same three shapes as the Partner API: see [Errors](/errors). servers: - url: https://app.sahlfinancial.com/api description: Console host. Same host as the Partner API. security: - dashboardSession: [] tags: - name: Bank connections description: Simulated in the Sandbox; 409 `bank_connect_unavailable` elsewhere. - name: Cases description: Client files that group documents, a score and a decision. - name: Documents description: Upload, status, result and download. - name: Webhooks description: Manage the endpoints that receive events. - name: API keys description: Create, rotate and revoke the keys used with the Partner API. - name: Scoring policies description: Weights and thresholds of the credit score. - name: Flows description: Verification flows (graphs) and their simulation. paths: /v1/bank-connections/{connection_id}/transactions: get: tags: - Bank connections summary: List the transactions of a bank connection description: >- **Who can call it:** Any signed-in member of the workspace. Six months of generated transactions, newest first, amounts in MAD. Not paginated. **Production behaviour.** No open-banking provider is live. This route answers `409` with the code `bank_connect_unavailable` unless the request is made in the Sandbox: send `X-Sahl-Environment: sandbox` (or `?environment=sandbox`). In the Sandbox the data is simulated and derived from the connection id; it is not read from a bank. A request with no environment is also refused. **Auth:** dashboard session (`Authorization: Bearer `). Not available with a partner API key. operationId: listBankConnectionTransactions parameters: - name: connection_id in: path required: true schema: type: string format: uuid title: Connection Id - name: environment in: query required: false schema: anyOf: - type: string - type: 'null' title: Environment - name: X-Sahl-Environment in: header required: false schema: anyOf: - type: string - type: 'null' title: X-Sahl-Environment responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TransactionListResponse' example: items: - id: txn-2026-09-salary date: '2026-09-25' description: VIREMENT SALAIRE OCP GROUP amount: 18120.5 type: credit category: salary balance: 31240.75 - id: txn-2026-09-000 date: '2026-09-03' description: VIREMENT LOYER amount: -4310 type: debit category: rent balance: 13120.25 total: 2 account_holder: Test Client bank_name: Attijariwafa bank '401': description: No session, expired token, ended session or inactive account. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: Invalid or expired token '403': description: >- The role is not allowed, MFA enrolment is pending, or the environment is refused. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: Insufficient permissions '404': description: Unknown connection. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: Bank connection not found '409': description: >- `bank_connect_unavailable`: not a Sandbox request, so no simulated data. No bank data provider is live. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: code: bank_connect_unavailable message: >- Bank connection is not available yet. No bank data provider is live for this workspace. '422': description: Validation error. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: - type: missing loc: - body - bank_code msg: Field required input: {} '429': description: >- More than 100 requests per minute from one IP address. The body has no `detail`. content: application/json: schema: $ref: '#/components/schemas/RateLimitError' example: code: rate_limit_exceeded message: Too many requests. Please slow down. headers: Retry-After: schema: type: integer description: Seconds to wait. components: schemas: TransactionListResponse: properties: items: items: $ref: '#/components/schemas/TransactionItem' type: array total: type: integer account_holder: anyOf: - type: string - type: 'null' bank_name: type: string type: object required: - items - total - account_holder - bank_name Error: type: object description: >- FastAPI error body. `detail` is a string, a list (422), or an object with `code` and `message` (extra keys possible). properties: detail: oneOf: - type: string - items: additionalProperties: true type: object type: array - type: object additionalProperties: true properties: code: type: string message: type: string required: - detail RateLimitError: type: object description: Top-level `code` and `message`, no `detail`. properties: code: type: string message: type: string required: - code - message TransactionItem: properties: id: type: string date: type: string description: type: string amount: type: number type: type: string category: type: string balance: type: number type: object required: - id - date - description - amount - type - category - balance securitySchemes: dashboardSession: type: http scheme: bearer bearerFormat: JWT description: >- The access token (JWT) of a signed-in console user, from `POST /v1/auth/login`. It lasts 30 minutes. It is not an API key: a partner API key is refused here. There is no cookie. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.