# Report Transactions

List your transactions

Endpoint: GET /report/transactions
Version: 2.0
Security: accountId, apiKey

## Query parameters:

  - `start_date` (string)
    Filter from this date (inclusive). The date and time must be provided in UTC, using the format Y-m-d H:i.

  - `end_date` (string)
    Filter until this date (inclusive). The date and time must be provided in UTC, using the format Y-m-d H:i.

  - `page` (number)
    Page Number

  - `records_per_page` (number)
    Limit records per page (Max: 2500)

## Response 200 fields (application/json):

  - `meta` (object, required)
    The Pagination object contains detailed information about the pagination of a collection of records.

This object is used to provide navigation and context for paginated results, allowing users to easily move between pages and understand the scope of the dataset.

  - `meta.page` (object, required)
    An object containing information about the pagination of pages within the collection.

  - `meta.page.current` (integer, required)
    The current page number being viewed.

  - `meta.page.total` (integer, required)
    The total number of pages available in the collection.

  - `meta.records` (object, required)
    An object containing information about the records within the collection.

  - `meta.records.total` (integer, required)
    The total number of records available in the collection.

  - `meta.records.per_page` (integer, required)
    The number of records displayed per page.

  - `meta.links` (object)
    An object containing URLs for navigation between different pages of the collection.

  - `meta.links.first` (string)
    The URL to the first page of the collection.

  - `meta.links.prev` (string)
    The URL to the previous page of the collection. This field is an empty string if there is no previous page.

  - `meta.links.next` (string)
    The URL to the next page of the collection. This field is an empty string if there is no next page.

  - `meta.links.last` (string)
    The URL to the last page of the collection.

  - `data` (array)

  - `data.id` (string)

  - `data.key` (string)
    Any value that will help the merchant manage the transaction on his database.

  - `data.date` (string)
    The date on which the provider reported the payment as having occurred.

  - `data.values` (object)

  - `data.values.requested` (integer)

  - `data.values.paid` (integer)

  - `data.values.fixed_fee` (number)

  - `data.values.variable_fee` (number)

  - `data.values.tax` (number)

  - `data.values.transfer` (number)

  - `data.transfer_date` (string)

  - `data.transfer_batch` (string)
    The batch where this transaction has transfered.

  - `data.method` (string)
    The payment method.

  - `data.document_number` (string)
    Unique document number used for Easypay Invoice.

  - `data.payment_type` (string)
    Enum: "single", "frequent", "subscription"

  - `data.payment_id` (string)

  - `data.payment_account` (object)

  - `data.payment_key` (string)

  - `data.payment_transaction_key` (string)
    Capture transaction key.

  - `data.descriptive` (string)
    Any descriptive information that will help the merchant manage the transaction on his database.

  - `data.created_at` (string)
    The timestamp indicating when the payment record was added to the system.

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