# Retrieve fee entries

Retrieves a list of fee entries.
> **Important:** This operation is experimental and may not be backward compatible.

Endpoint: GET /fees
Version: latest
Security: SecretApiKey, JWT

## Security:

  - `SecretApiKey` (unknown)
    apiKey in header REB-APIKEY

  - `JWT` (unknown)
    http bearer JWT

## Query parameters:

  - `limit` (integer)
    Limit the number of collection items to be returned.
Use `0` to return an empty collection and still receive the count of matching items in `Pagination-Total`.

  - `offset` (integer)
    Specifies the starting point within the collection of items to be returned.

  - `filter` (string)
    Criteria for filtering collection items.
This field requires a special format.
Use `,` to specify multiple allowed values.
Use `;` to specify multiple fields.

For more information, see [Search filters](https://www.rebilly.com/docs/dev-docs/search-filters).

  - `sort` (array)
    Sorts and orders the collection of items. To sort in descending
order, prefix with `-`. Multiple fields can be sorted by separating each with `,`.

## Response 200:

  - `200` (unknown)
    List of fee entries retrieved.

## Response 200 fields (application/json):

  - `id` (string)
    ID of the fee.
    Example: fee_01GQT145JX3XBRJ8K812Y3GRE9

  - `type` (string, required)
    Type of fee.
    Enum: "buy", "sell"

  - `name` (string, required)
    Name of the fee.
    Example: A gateway fee

  - `filter` (string | null)
    Filter that is based on the properties of the transaction and used to determine when to apply the fee.
    Example: type:sale,capture;result:approved

  - `formula` (object, required)
    Formula that is used to calculate the fee.

  - `formula.type` (string, required)
    Type of fee.
    Enum: "fixed-fee"

  - `formula.currency` (string, required)
    Currency code in ISO 4217 format.
    Example: USD

  - `formula.amount` (number, required)
    Amount of the fee.
    Example: 10

  - `formula.bips` (number, required)
    Basis points.
Example: 100 bips = 1%, 1 bip = 0.01%.
    Example: 100

  - `formula.minAmount` (number)
    Minimum fee amount.
This value is applied when the calculated fee is less than the required minimum.
    Example: 10

  - `settlementSettings` (any)
    Fee settlement settings.
This value overrides the gateway account financial settings of the transaction.

  - `settlementSettings.settlementPeriod` (object, required)
    Instruction for calculating the settlement time.
The settlement time and settlement period anchor are used
in conjunction with the transaction processed time,
to calculate the time in which the amount settles.

  - `settlementSettings.settlementPeriod.method` (string, required)
    Enum: "date-interval"

  - `settlementSettings.settlementPeriod.duration` (integer, required)
    Number of time units.

  - `settlementSettings.settlementPeriod.unit` (any, required)
    Unit of time.

  - `settlementSettings.settlementPeriod.anchor` (object)
    Instruction for calculating the period anchor.

  - `settlementSettings.settlementPeriod.anchor.method` (string, required)
    Enum: "day-of-month"

  - `settlementSettings.settlementPeriod.anchor.day` (integer, required)
    Day of the month in which the event occurs.
If the month has less days, the last day of the month is selected.

  - `settlementSettings.settlementPeriod.anchor.time` (string)
    Extended ISO-8601 format of time.

  - `settlementSettings.settlementPeriod.anchor.day` (string, required)
    Day of the week when the event occurs.
    Enum: "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"

  - `settlementSettings.settlementPeriod.anchor.week` (string, required)
    Enum: "next", "first-in-month", "last-in-month"

  - `settlementSettings.advancedSettings` (array)
    Advanced settlement settings.
Use these settings to override either default settlement currency,
period, or both for the transactions matched a filter.

  - `settlementSettings.advancedSettings.filter` (string, required)
    Filter that is based on transaction properties and is used to determine when to apply the settings.
    Example: currency:EUR,GBP

  - `createdTime` (string)
    Date and time when the resource is created.
This value is set automatically when the resource is created.

  - `updatedTime` (string)
    Date and time when the resource is updated.
This value is set automatically when the resource is updated.

  - `_links` (array)
    Related links.

  - `_links.href` (string)
    Link URL.

  - `_links.rel` (string)
    Type of link.
    Enum: "self"

## Response 200 headers (application/json):

  - `Pagination-Total` (integer)
    Total number of items that match the request.
The value is independent of `limit`, including when `limit` is `0`.
    Example: 332

  - `Pagination-Limit` (integer)
    Maximum number of items per page.
    Example: 100

  - `Pagination-Offset` (integer)
    Specifies the starting point within the
collection of resource results. For example, a request with
`limit=20` retrieves and displays the first 20 results on a page. A
following request with `limit=20` and `offset=20`, retrieves the next
page of 20 results.
    Example: 2

## Response 401:

  - `401` (unknown)
    Unauthorized access.
Invalid credentials used.

## Response 401 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.

## Response 403:

  - `403` (unknown)
    Access forbidden.

## Response 403 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.