> This page is for version v2026-04-01 (default).
> For other versions, use one of these documentation indexes:
> - v2026-04-01 (default): https://docs.givechariot.com/v2026-04-01/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.givechariot.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.givechariot.com/_mcp/server.

# Get account statement

GET https://api.givechariot.com/fdx/v6/accounts/{id}/statements/{statementId}

Retrieve a statement document. Use the Accept header to specify the desired format. Supported formats are PDF (default), CSV, and BAI2.

Reference: https://docs.givechariot.com/fdx/statements/get-document

## Authentication

- `Authorization` header (bearer token, required) — OAuth 2.0 Bearer token. The FDX API is read-only and requires the read_only scope. See the Authentication page for token exchange details.

## Servers

- `https://api.givechariot.com/fdx/v6` (Production, default)
- `https://devapi.givechariot.com/fdx/v6` (Staging)

## Request

### Path parameters

- `id` (string, required) — Unique identifier for the account
- `statementId` (string, required) — Unique identifier for the statement

## Response

### 200

The statement document in the requested format

- File download.

## Errors

### 400 Bad Request Error

Invalid request parameters

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem

### 401 Unauthorized Error

Missing or invalid OAuth 2.0 Bearer token

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem

### 403 Forbidden Error

Insufficient permissions or IP not whitelisted

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem

### 404 Not Found Error

Resource not found

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem

### 406 Not Acceptable Error

The requested media type in the Accept header is not supported

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem

### 500 Internal Server Error

Unexpected server error

- `type` (string, required) — A URI reference that identifies the problem type
- `title` (string, required) — A short human-readable summary of the problem type
- `status` (integer, required) — The HTTP status code
- `detail` (string, optional) — A human-readable explanation specific to this occurrence of the problem
- `instance` (string, optional) — A URI reference that identifies the specific occurrence of the problem