API referenceWebhooksEvent catalogBatchesbatch.expired

batch.expired

⚠️
Preview — this feature is being built; the design below is the spec.

Sent when: The 24-hour window ended before every request ran. Requests that finished are in the output file; the rest are marked expired.

PropertyValue
ScopeOne workspace. Register with an inference key at /v1/webhooks.
AreaBatches
Subscribe with"events": ["batch.expired"], or a prefix such as "batch.*"

Payload

{
  "id": "evt_01JCA5D7F9H1K3M5P7R9",
  "type": "batch.expired",
  "created_at": "2026-11-05T10:00:00Z",
  "workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
  "data": {
    "object": {
      "id": "batch_01JBXF3P8K",
      "type": "batch",
      "status": "expired",
      "output_file_id": "file_01JBXG7Q",
      "request_counts": {
        "total": 5000,
        "succeeded": 4120,
        "failed": 0,
        "canceled": 880
      }
    }
  }
}

data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.

What to do

  • Collect the finished results, then resubmit the expired custom_ids in a smaller batch.
  • Only the requests that ran are billed.

Delivery

Deliveries are signed, retried with back-off for up to 3 days, and may arrive more than once or out of order. De-duplicate on the syntic-event-id header and compare timestamps before acting. See Webhooks.

batch.failedbatch.canceled
Was this page helpful?