Skip to main content
POST
Sync Integration
Queue a manual re-sync: customers and revenue for a payment provider, the user backfill for Supabase, or the event-history import for PostHog. Supported for Stripe, Polar, Paddle, Dodo, Creem, Chargebee, Whop, Supabase, and PostHog. Other providers re-sync from the dashboard, because their backfills need credentials and configuration selected at connect time. For PostHog this re-runs the event-history import against the personal API key, region, and project stored at connect time, and it is the supported way to retry a failed import. The import restarts from the beginning; already-imported events carry the same IDs the live webhook uses, so a re-run cannot duplicate them. Historical events never trigger automations. You get a 409 while an import is queued or syncing; terminal BullMQ failures release that state for retry. For Supabase this reads the project, schema, and table already configured for the integration - it cannot be pointed at a different table, and it returns 400 when no table has been configured yet. Run it after connecting Supabase: the database trigger only sends rows that change after it is installed, so users who existed before that have no attributes in Sequenzy until a backfill runs. The call returns immediately. Poll Get Integration to watch syncStatus and lastSyncAt, and List Integration Activity for per-row outcomes. Requires an API key with the integrations:manage scope.

Request

string
required
Integration ID, from List Integrations.
This endpoint takes no request body.

Response fields

string
Background job ID for the queued sync, or null when no job ID was returned.
string
Sync status after queueing, always queued on success.
object
Supabase only: the projectRef, schema, and table the backfill reads. Absent for providers whose sync has no configurable source.

Responses