Backward-compatible release: All changes are additive or relax existing constraints. No existing integrations are affected.
Schedule backfill enhancements
POST /v2/integrations/connections/schedules/backfill has two new capabilities in this release.
resource is now optional
Previously, resource was a required field and you had to name a specific resource type (such as VEHICLE or HOS) to run a backfill. It is now optional.
When you omit resource, the endpoint syncs every active connection against the full adapter registry: each connection gains whatever schedules its TSP has implemented adapters for and is currently missing. This makes it straightforward to bring all connections up to date after a new adapter is deployed, without needing to know which resource types were added.
New dry_run flag
A new optional boolean field dry_run lets you preview which connections would receive new schedules without actually creating any rows. The response returns the same connection_ids list as a live run, but no schedules are written to the database.
dry_run to false or omit it entirely to perform the backfill for real.
Summary of request body changes
Need help?
API reference
View complete endpoint documentation for the Integrations API
Contact support
Questions about this release? Our team is here to help