# Retrieve payout request timeline messages

Retrieves a list of payout request timeline messages.

Endpoint: GET /payout-requests/{id}/timeline
Version: latest
Security: SecretApiKey, JWT

## Path parameters:

  - `id` (string, required)
    ID of the resource.

## Query parameters:

  - `limit` (integer)
    Limits the number of collection items to be returned.

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

  - `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 ,.

  - `q` (string)
    Use this field to perform a partial search of text fields.

## Response 200 fields (application/json):

  - `id` (string, required)
    ID of the message.
    Example: "tlm_0YVDMDE2BMC6KBB5MX76RF6T80"

  - `type` (string, required)
    Type of timeline event.
    Enum: "timeline-comment-created", "payout-request-created", "payout-request-flushed", "payout-request-flush-undone", "payout-request-approved", "payout-request-approval-undone", "payout-request-allocated", "payout-request-processing-started", "payout-request-fulfilled", "payout-request-canceled", "payout-request-reversed", "payout-request-blocked", "payout-request-unblocked"

  - `occurredTime` (string, required)
    Date and time when the timeline event occurred.

  - `triggeredBy` (string, required)
    Who or what triggered this event.
    Enum: "rebilly", "app", "direct-api"

  - `message` (string, required)
    Human-readable message describing the timeline event.

  - `extraData` (object, required)
    Additional data.

  - `extraData.actions` (array)
    Actions available for a timeline message.
If no actions are available, this field is empty.

  - `extraData.tables` (array)
    Table data that is attached to the timeline message.

  - `extraData.tables.type` (string)
    Enum: "list", "one-columns", "two-columns", "three-columns"

  - `extraData.tables.title` (string)
    Data table title.

  - `extraData.tables.footer` (string)
    Data table footer.

  - `extraData.author` (object)
    Author of the timeline message.

  - `extraData.author.userFullName` (string)
    Full name of the author.

  - `extraData.author.userId` (string)
    ID of the author.
    Example: "usr_0YVCEENYJ3D7Q9EN6BN16HA0G4"

  - `extraData.mentions` (object)
    User mentions, or tags, in a timeline.
    Example: {"@test@mail.com":"userId-1"}

  - `extraData.links` (array)
    Links that are attached to a timeline message.

  - `extraData.links.resourceType` (string)
    Enum: "kyc-document", "invoice", "subscription", "transaction", "email-message", "dispute", "coupon", "external"

  - `extraData.links.resourceId` (string)
    Unique resource ID.

  - `extraData.links.placeholder` (string)
    Example: "KYC document"

  - `extraData.links.externalUrl` (string)
    Example: "http://example.com"

## 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 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 404 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 429 fields (application/json):

  - `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".
    Example: "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.
    Example: "Rate Limit Exceeded"

  - `status` (integer)
    HTTP status code.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.
    Example: "A request cannot be executed because the user has sent too many requests within a certain period of time"

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