API endpointsBackfill requestsList the Organization's backfill requests, newest first, optionally narrowed to one Connected Profile and one status GET

List the Organization's backfill requests, newest first, optionally narrowed to one Connected Profile and one status

GET
/v1/backfill-requests

List the Organization's backfill requests, newest first, optionally narrowed to one Connected Profile and one status.

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Query Parameters

limit?integer
Range1 <= value <= 100
cursor?string

Opaque cursor for fetching the next result page.

Length1 <= length
connectedProfileId?string

Koil Connected Profile identifier.

Length1 <= length
status?||||

Response Body

application/json

application/json

curl -X GET "https://example.com/v1/backfill-requests"
{  "data": [    {      "backfillRequestId": "bf_2Jd8kQm4ZtPw7XcR1nVb",      "connectedProfileId": "cp_123",      "contentType": "instagram.media.items",      "since": "2026-06-01T00:00:00.000Z",      "maxItems": 1000,      "status": "completed",      "stopReason": "reached_since",      "emitted": 212,      "fetched": 240,      "skipped": 28,      "oldestEmittedAt": "2026-06-01T08:14:03.000Z",      "startedAt": "2026-07-01T10:00:01.000Z",      "completedAt": "2026-07-01T10:02:37.000Z",      "createdAt": "2026-07-01T10:00:00.000Z",      "updatedAt": "2026-07-01T10:02:37.000Z"    }  ],  "nextCursor": "WyIyMDI2LTA3LTAxVDEwOjAwOjAwLjAwMFoiLCJiZl8ySmQ4a1FtNFp0UHc3WGNSMW5WYiJd",  "hasMore": true}
{  "error": {    "code": "validation_error",    "message": "string",    "meta": {      "property1": null,      "property2": null    }  }}

Rotate an Auth Integration OAuth client secret POST

Rotate an Auth Integration OAuth client secret.

Submit one or more backfill requests, each for one content type's history on one Connected Profile POST

Submit one or more backfill requests, each for one content type's history on one Connected Profile. Historical items are delivered as ordinary `content.*` events; nothing is stored. Validation is atomic across the submission and every item then runs independently. Requires an `Idempotency-Key`; one run per content type per profile may be in flight at a time.