---
title: "Search Callbacks"
method: GET
path: "/callbacks"
tags: ["Callbacks"]
---

# Search Callbacks

`GET /callbacks`

## Request

- Base URL: `https://partner-api.getpliant.com/api`
- URL: `https://partner-api.getpliant.com/api/callbacks`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/getpliant/apis/pliant-customer-api/docs/callbacks/get.ts> (a function with typed inputs; its response is checked against the schema)

Get a list of all callbacks we produced for you, whether we could send them to you or not. This log contains all callbacks Pliant produced, together with a status and further metadata to let you investigate problems etc. You can add optional filters to narrow down the results. To get the payload of a specific callback, use the [`GET /callbacks/{callbackId}`](/reference/get-callback) endpoint. To re-trigger delivery of one or more callbacks, use the [`POST /callbacks/resend`](/reference/resend-callbacks) endpoint.

## Query parameters

- `organizationId` string, uuid
- `entityId` string, uuid
- `entityIds` string[]
- `eventType` string
- `status` 'UNSENT' | 'IN_PROGRESS' | 'SENT' | 'FAILED' | 'SKIPPED' | 'TO_BE_SEND_IMMEDIATELY'
- `fromDate` string, date-time
- `toDate` string, date-time
- `byDateField` 'createdAt' | 'sentAt'
- `limit` integer
- `page` integer
- `sortBy` 'organizationId' | 'status' | 'eventType' | 'createdAt'
- `sortDirection` 'ASC' | 'DESC'

## Response `200`

Ok

- object
  - `data` object[]: Callback log entries, sorted and filtered according to the request parameters.
    - `id` string, uuid, required: The ID of the callback log entry.
    - `entityId` string, uuid, required: The ID of the entity the callback is about. Together with the `eventType`, this uniquely identifies the business entity.
    - `eventType` string, required: The type of the event that triggered the callback.
    - `organizationId` string, uuid, required: The ID of the organization the callback is about.
    - `status` 'UNSENT' | 'IN_PROGRESS' | 'SENT' | 'FAILED' | 'SKIPPED' | 'TO_BE_SEND_IMMEDIATELY', required: The status of the callback. The callback starts as `UNSENT`, transitions to `IN_PROGRESS`, then to `SENT` or `FAILED`. If the callback is skipped (mostly due to manual interventions), it will be marked as `SKIPPED`. The status `TO_BE_SEND_IMMEDIATELY` is a short-lived, intermediate status similar to `UNSENT`.
    - `httpEndpoint` string, nullable: The HTTP endpoint from the partners backend that was called for this callback.
    - `httpResponseCode` string, nullable: The latest HTTP response code from the partners backend for this callback.
    - `attemptCount` integer, nullable: The amount of attempts to send the callback, includes retries.
    - `createdAt` string, date-time, required: The date and time when the callback was created in Pliant's database.
    - `sentAt` string, date-time, nullable: The date and time when the callback was successfully sent to the partners backend.
  - `hasNextPage` boolean: Indicates whether there is a next page available.

## Other responses

- `400` (unresolved $ref)
- `401` (unresolved $ref)
- `403` (unresolved $ref)
- `429` (unresolved $ref)
- `500` (unresolved $ref)

## Changes

- **2026-11-03** `a4fbf7d068b4`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/getpliant/apis/pliant-customer-api/changes/callbacks/get.md)

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) - [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/getpliant/apis/pliant-customer-api/revisions/a4fbf7d068b4?raw)