Skip to main content
Released 3rd August 2026

Document resource support

This release extends the resource enum across the Integrations API to include document as a supported resource type. All endpoints that accept or return a resource field now recognise this new value.
Backward-compatible addition: Existing integrations are unaffected. The document value is purely additive — no existing enum values were removed or renamed.

New enum value: document

The ResourceEnum schema has been extended with a new value: This change propagates across all endpoints that reference ResourceEnum, including request bodies, query parameters, and response payloads.

Affected endpoints

The resource field in schedule-related endpoints now accepts and returns document.Endpoints updated:
  • GET /v2/integrations/connections/{connection_id}/schedules — resource query parameter and response items
  • POST /v2/integrations/connections/{connection_id}/schedules — resource in request body and response
  • GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id} — resource in response
  • PATCH /v2/integrations/connections/{connection_id}/schedules/{schedule_id} — resource in response
  • POST /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/activate — resource in response
  • POST /v2/integrations/connections/{connection_id}/schedules/activate-schedules — resource in response
  • POST /v2/integrations/connections/schedules/backfill — resource in request body
Example — create a schedule for documents:
The resource field in resource operation endpoints now accepts and returns document.Endpoints updated:
  • GET /v2/integrations/connections/resource-operations — resource query parameter and response items
  • GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id} — resource in response
Example — filter resource operations by document:
The resource field in execution responses now includes document.Endpoints updated:
  • GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions — resource in response items
The resource field in the data freshness response now includes document.Endpoints updated:
  • GET /v2/integrations/connections/data-freshness — resource in response items

Webhook Sorting Support

This release adds sorting support to the webhook and webhook log listing endpoints, giving you control over the order in which results are returned.
Backward-compatible: All changes in this release are additive. No existing integrations are affected.

New Features

GET /v2/notifications/webhooks now accepts two new optional query parameters:Example:
GET /v2/notifications/webhooks/{webhook_id}/logs now accepts two new optional query parameters:Example:

Need help?

API reference

View complete endpoint documentation for the Integrations API

Contact support

Questions about this release? Our team is here to help