Skip to main content
POST
Force Resync Connector

Overview

This guide demonstrates how to use the Resync API to force a sync of a connector.
It is neither necessary nor recommended to call this endpoint periodically. Bindbee automatically performs periodic syncs for you. You should only trigger a resync in specific cases, such as when a user manually initiates a sync from your application (e.g., by clicking a “Sync” button).
To work out whether a resync is the right fix, read the connector’s per-model breakdown first - see Sync status. Resyncing clears transient and size-related failures; a permission gap needs fixing upstream before the next run will help.

Authorizations

Authorization
string
header
default:<BINDBEE_API_KEY>
required

Your Bindbee API key, sent as Authorization: Bearer <BINDBEE_API_KEY>. Required on every request.

X-Connector-Token
string
header
default:<CONNECTOR_TOKEN>
required

The connector token for one customer's connection. This is not your Bindbee API key. Required on requests that read or write a single customer's data.

Response

Successful Response

The response is of type string.