How do I trigger a resync?
Updated 4 days ago
Trigger a resync with Force Sync on the connector in the dashboard, or by calling the Force Resync API. Both work on Production and Development connectors.
Resync from the dashboard
Open Connectors and select the connector.
On the Overview tab, click Force Sync.
Force Sync is unavailable while a sync is already running or when the connector shows Relink Needed.
Resync through the API
Call the Force Resync endpoint with your API key and the connector's token in the header:
curl --request POST \
--url 'https://api.bindbee.dev/api/embedded/v1/connectors/resync' \
--header 'Authorization: Bearer <BINDBEE_API_KEY>' \
--header 'X-Connector-Token: <CONNECTOR_TOKEN>'A successful call returns 200 with the message Data Syncing Started. The sync then runs in the background. To know when the data has landed, listen for the connector_synced webhook or check sync_status until it returns to Done.
When to resync
Your customer changed something in their HR system and expects to see it now.
You wrote data to the source system and need a sync to make it readable through our API.
You're using a Development connector, which never syncs on a schedule.
You're investigating a data discrepancy for one customer.
Don't call the resync endpoint on a timer. Production connectors already sync automatically. Trigger a resync only in response to a specific need, such as a user clicking a sync button in your product.
If a resync fails the same way again
Open the connector's Sync tab and read the per-model breakdown. A resync clears temporary and size-related failures, but a permission gap in the source system has to be fixed there first. Resync rather than deleting and recreating the connector: a new connector gives every record a new Bindbee ID.