---
title: "Retrieve single statement based on unique id provided"
method: GET
path: "/Statements/{statementId}"
tags: ["BankFeeds"]
---

# Retrieve single statement based on unique id provided

`GET /Statements/{statementId}`

By passing in a statement id, you can search for matching statements

## Path parameters

- `statementId` string, uuid, required

## Response `200`

search results matching id for single statement

- Statement
  - `id` string, uuid — GUID used to identify the Statement.
  - `feedConnectionId` string, uuid — The Xero generated feed connection Id that identifies the Xero Bank Account Container into which the statement should be delivered. This is obtained by calling GET FeedConnections.
  - `status` 'PENDING' | 'REJECTED' | 'DELIVERED' — Current status of statements
  - `startDate` string, date — Opening balance date (can be no older than one year from the current date) ISO-8601 YYYY-MM-DD
  - `endDate` string, date — Closing balance date ISO-8601 YYYY-MM-DD
  - `startBalance` StartBalance — The starting balance of the statement
    - `amount` number, double — decimal(19,4) unsigned Opening/closing balance amount.
    - `creditDebitIndicator` 'CREDIT' | 'DEBIT' — If the statement balances are credit or debit, the CreditDebitIndicator should be specified from the perspective of the Customer.
  - `endBalance` EndBalance — The StartBalance plus all the Statement Line Amounts should be equal to the EndBalance Amount.
    - `amount` number, double
    - `creditDebitIndicator` 'CREDIT' | 'DEBIT' — If the statement balances are credit or debit, the CreditDebitIndicator should be specified from the perspective of the Customer.
  - `statementLines` StatementLine[]
    - `postedDate` string, date — The date that the transaction was processed or cleared as seen in internet banking ISO-8601 YYYY-MM-DD
    - `description` string — Transaction description
    - `amount` number, double — Transaction amount
    - `creditDebitIndicator` 'CREDIT' | 'DEBIT' — If the statement balances are credit or debit, the CreditDebitIndicator should be specified from the perspective of the Customer.
    - `transactionId` string — Financial institute's internal transaction identifier. If provided this field is factored into duplicate detection.
    - `payeeName` string — Typically the merchant or payee name
    - `reference` string — Optional field to enhance the Description
    - `chequeNumber` string — The cheque/check number
    - `transactionType` string — Descriptive transaction type
  - `errors` Error[]
    - `title` string — Human readable high level error description.
    - `status` integer — The numeric HTTP Status Code, e.g. 404
    - `detail` string — Human readable detailed error description.
    - `type` 'invalid-request' | 'invalid-application' | 'invalid-feed-connection' | 'duplicate-statement' | 'invalid-end-balance' | 'invalid-start-and-end-date' | 'invalid-start-date' | 'internal-error' | 'feed-already-connected-in-current-organisation' | 'invalid-end-date' | 'statement-not-found' | 'feed-connected-in-different-organisation' | 'feed-already-connected-in-different-organisation' | 'bank-feed-not-found' | 'invalid-country-specified' | 'invalid-organisation-bank-feeds' | 'invalid-organisation-multi-currency' | 'invalid-feed-connection-for-organisation' | 'invalid-user-role' | 'account-not-valid' | 'feed-not-found-or-already-deleted' — Identifies the type of error.
  - `statementLineCount` integer

## Other responses

- `404` — Statement not found

---

[API](https://skmtc.net/xeroapi/apis/xero-bank-feeds-api.md) · [All operations](https://skmtc.net/xeroapi/apis/xero-bank-feeds-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/xeroapi/xero-bank-feeds-api/versions/a542ef112adf/schema)