---
title: "View history of a payable"
method: GET
path: "/payables/{payable_id}/history"
tags: ["Payables"]
---

# View history of a payable

`GET /payables/{payable_id}/history`

## Request

- Base URL: `https://api.sandbox.monite.com/v1`
- URL: `https://api.sandbox.monite.com/v1/payables/{payable_id}/history`
- Auth: HTTP bearer

Returns a chronological list of events related to the specified payable.  This includes changes in status, updates to data, comments, and actions taken  by users or automation rules.

## Path parameters

- `payable_id` string, required

## Query parameters

- `order` 'asc' | 'desc'
- `limit` integer
- `pagination_token` string
- `sort` 'timestamp'
- `event_type__in` 'status_changed' | 'payable_created' | 'payable_updated' | 'credit_note_linked' | 'credit_note_unlinked' | 'file_attached'
- `entity_user_id__in` string, uuid
- `timestamp__gt` string, date-time
- `timestamp__lt` string, date-time
- `timestamp__gte` string, date-time
- `timestamp__lte` string, date-time

## Headers

- `x-monite-version` string, required
- `x-monite-entity-id` string, required

## Response `200`

Successful Response

- PayableHistoryPaginationResponse: A paginated list of change history records.
  - `data` PayableHistoryResponse[], required
    - `id` string, uuid, required: A unique ID of the history record.
    - `entity_user_id` string, uuid: ID of the entity user who made the change or trigger the event, or `null` if it was done by using a partner access token.
    - `event_data` union, required: An object containing additional information about the event or change. The object structure varies based on the `event_type`.
      - PayableStatusChangedEventData
        - `new_status` 'draft' | 'new' | 'approve_in_progress' | 'waiting_to_be_paid' | 'partially_paid' | 'paid' | 'canceled' | 'rejected', required
        - `old_status` 'draft' | 'new' | 'approve_in_progress' | 'waiting_to_be_paid' | 'partially_paid' | 'paid' | 'canceled' | 'rejected', required
      - PayableUpdatedEventData
      - PayableCreatedEventData
        - `payable_source` 'upload' | 'email' | 'einvoicing', required
      - PayableCreditNoteLinkedEventData
        - `credit_note_document_id` string
        - `credit_note_id` string, required
      - PayableCreditNoteUnlinkedEventData
        - `credit_note_document_id` string
        - `credit_note_id` string, required
      - FileAttachedEventData
        - `file_name` string, required
        - `file_size` integer, required
        - `url` string, required
    - `event_type` 'status_changed' | 'payable_created' | 'payable_updated' | 'credit_note_linked' | 'credit_note_unlinked' | 'file_attached', required
    - `payable_id` string, uuid, required: ID of the payable document that was changed or triggered an event.
    - `timestamp` string, date-time, required: UTC date and time when the event or change occurred.
  - `next_pagination_token` string: A token that can be sent in the `pagination_token` query parameter to get the next page of results, or `null` if there is no next page (i.e. you've reached the last page).
  - `prev_pagination_token` string: A token that can be sent in the `pagination_token` query parameter to get the previous page of results, or `null` if there is no previous page (i.e. you've reached the first page).

## Other responses

- `400`: Bad Request
- `401`: The `Authorization` header is missing or contains an invalid or expired access token. See [Authentication](https://docs.monite.com/api/concepts/authentication) to learn how to authenticate API calls.
- `403`: The specified access token does not have permissions to perform this operation.
- `404`: A payable with the specified ID was not found.
- `422`: Validation Error
- `429`: API rate limit has been exceeded. Check the response headers for the rate limit information.

---

[API](https://skmtc.dev/monite/apis/monite-2.md) - [All operations](https://skmtc.dev/monite/apis/monite-2/llms.txt) - [OpenAPI document](https://skmtc.dev/monite/apis/monite-2/revisions/4299ccf95edb?raw)