# Show customer details

Retrieves the customer details, including reward balances.
**Required scope:** customer:read

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

## Security:

  - `accountId` (unknown)
    apiKey in header AccountId

  - `apiKey` (unknown)
    apiKey in header ApiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Response 200:

  - `200` (unknown)
    OK

## Response 200 fields (application/json):

  - `id` (string)
    Unique identifier for the customer.
    Example: 649e88cf-0b78-4c36-8f99-33f5ebb812a1

  - `name` (string)
    Full name of the customer.
    Example: John Doe

  - `email` (string)
    Customer's email address.
    Example: john.doe@example.com

  - `phone` (string)
    The contact phone number of the customer, excluding the country code indicator.
    Example: 911234567

  - `phone_indicative` (string)
    The country code indicator for the customer's phone number.
    Example: +351

  - `fiscal_number` (string)
    Customer's tax identification number or fiscal number.
    Example: PT123456789

  - `key` (string)
    A customizable text field for users to input their own identifier for the customer.
    Example: customer Key Example

  - `language` (string)
    Preferred language for customer communications. Uses ISO 639-1 language codes.
    Enum: "PT", "EN", "ES"

  - `reward_balances` (array)
    Reward balances across all reward accounts for this customer. Empty array if no reward accounts exist. See the [Rewards & Redemptions guide](/docs/guides/rewards-and-redemptions) for the full flow.

  - `reward_balances.account_id` (string)
    The unique identifier of the reward account.
    Example: 458b2fc4-3092-4de3-abd4-fe1600c09420

  - `reward_balances.available_balance` (number)
    The available reward balance for this account.
    Example: 12.5

## Response 401:

  - `401` (unknown)
    Unauthorized

## 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:

  - `403` (unknown)
    Forbidden

## 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 403 fields (application/xml):

  - `message` (array)

## Response 404:

  - `404` (unknown)
    Not Found

## 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 429:

  - `429` (unknown)
    Too Many Requests

## 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:

  - `500` (unknown)
    Internal Server Error

## 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.

## Response 200 examples:

  - `Success` (unknown)
    Success

## Response 401 examples:

  - `Wrong credentials provided` (unknown)

## Response 403 examples:

  - `Wrong credentials provided` (unknown)

## Response 404 examples:

  - `Resource not found` (unknown)

## Response 429 examples:

  - `Rate limit exceeded` (unknown)

## Response 500 examples:

  - `Internal error` (unknown)