# List fee transactions for an account

Returns an array containing all fee transactions created for the account specified in the request URL.

Endpoint: GET /v1/accounts/{account_id}/transactions/fees
Version: 1.0

## Path parameters:

  - `account_id` (string, required)

## Query parameters:

  - `page[number]` (integer)
    The number of results pages to return.

  - `page[size]` (string)
    The size of each page in the response.

  - `filter[type]` (string)
    Filter the results by the type of fee collected.

  - `filter[reconciliation_id]` (string)
    Filter the results by a transactions reconciliation ID. (Effectively allows you to look up the transaction of one fee booking.)

  - `filter[solaris_initiated]` (boolean)
    Filter the results to indicate whether  initiated the fee transaction.

## Response 200 fields (application/json):

  - `type` (string)
    The type of fee. Note that you may only collect the types of fees that have been enabled for you.
    Example: "ChargeAccountMaintenance"

  - `amount` (object)
    The amount of the fee transaction.

  - `amount.value` (integer)
    Example: 499

  - `amount.currency` (string)
    Example: "EUR"

  - `reconciliation_id` (string)
    An ID linking a fee transaction to an account booking for reconciliation.
    Example: "938cfdf93ef54bdcbd4e955584da3bf0fct"

  - `initiator_reference` (string)
    Optional reference for the fee transaction to be populated by you.
    Example: "2022_08_acct_maint"

  - `original_transaction_id` (string)
    Optional ID to be provided for fee types that relate to or are charged for individual transactions. In this case, you would provide the ID of the booking linked to the transaction.
    Example: "6d4659e500ef4b10aa48d6b08d0d3e7b"

  - `solaris_initiated` (boolean)
    A field to indicate whether the fee transaction solaris initiated or not.

  - `valuta_date` (string)
    Optional valuta date provided by client. If both 'original_transaction_id' and 'valuta_date' are provided in the request payload, the provided valuta_data will be used.
    Example: "2023-06-01"

## Response 400 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `code` (string)
    Example: "invalid_request"

  - `title` (string)
    Example: "Invalid Request"

  - `details` (string)
    Example: "Request is invalid"

## Response 403 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `code` (string)
    Example: "unauthorized_action"

  - `title` (string)
    Example: "Unauthorized Action"

  - `details` (string)
    Example: "Unauthorized action is not allowed."

## Response 404 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `code` (string)
    Example: "model_not_found"

  - `title` (string)
    Example: "Model Not Found"

  - `details` (string)
    Example: "Model was not found"

## Response 500 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `code` (string)
    Example: "generic_error"

  - `title` (string)
    Example: "Internal Server Error"

  - `details` (string)
    Example: "Internal server error occurred"