# Retrieve a settlement

Retrieve a single settlement by its ID.
**Required scope:** <code style="background:#e8f0fe;color:#1a73e8;padding:2px 8px;border-radius:12px;font-size:0.85em">settlement:read</code>

Endpoint: GET /settlement/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    The unique identifier of the settlement to retrieve.

## Response 200 fields (application/json):

  - `id` (string, required)
    Unique identifier for the settlement.
    Example: f6a7b8c9-d0e1-2345-fabc-456789012306

  - `created_at` (string, required)
    Timestamp when the settlement was created. Always present.
    Example: 2026-02-05T09:30:00Z

  - `updated_at` (string | null, required)
    Timestamp when the settlement was last updated, or `null` when it has never been updated.
    Example: 2025-10-01T00:00:00Z

  - `name` (string, required)
    Human-readable name of the settlement (its batch reference).
    Example: 1006

  - `description` (string, required)
    Human-readable description of the settlement.
    Example: EASYPAY-1977225-42185-161-998590696

  - `status` (string, required)
    Current status of the settlement.
    Enum: "IN_TRANSIT", "SUCCEEDED", "FAILED"

  - `total_amount` (object, required)
    The money type is a data structure used to represent a monetary value in a specific currency. It includes both the amount and the currency type to accurately define the value of money in various contexts, such as financial transactions, pricing, and accounting.

  - `total_amount.amount` (string)
    Represents the numerical value of the money. The amount should be a string formatted to include up to two decimal places to accurately represent cents or subunits of currency. For example, "123.45" represents one hundred twenty-three units and forty-five subunits of the currency.

  - `total_amount.currency` (string)
    Indicates the type of currency associated with the amount. This should follow standard currency codes (ISO 4217), such as "USD" for US Dollar, "EUR" for Euro, or "JPY" for Japanese Yen, to specify which currency the amount is denominated in.

  - `number_of_items` (integer, required)
    Number of transactions included in the settlement.
    Example: 2

  - `destination` (object, required)
    Where the settled funds are sent.

  - `destination.type` (string, required)
    Type of destination.
    Enum: "IBAN"

  - `destination.details` (object)
    Details specific to the destination type.

  - `destination.details.iban` (string)
    Destination IBAN. Omitted when empty.
    Example: PT50007974951304464003280

## Response 401 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 404 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 412 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.