Re-sync Connector Data (Historical Sync)
Triggers a full historical sync of a connector or multiple schema tables within a connector. If the connector is paused, the table sync will be scheduled to be performed when the connector is re-enabled. If there is a data sync already in progress, we will try to complete it. If it fails, the request will be declined and the HTTP 409 Conflict error will be returned.
Request schema
Path parameters
connectorId
stringrequired
The unique identifier for the connector within the Fivetran system
example:
Header parameters
Authorization
stringrequired
HTTP: basicAuth
HTTP AuthorizationScheme: basic
Accept
string
default:
example:
Request
scope
object
A map containing an array of tables to re-sync for each schema.
It is an optional parameter that must be non-empty if provided. If not provided, all schemas and tables of the connector are re-synced.
schema
array
Schema name
example:
type:
Http + 1.1
POST
https://api.fivetran.com/v1/connectors/connector_id/resync
POST /v1/connectors/connector_id/resync HTTP/1.1
Accept: application/json;version=2
Authorization: Basic REPLACE_BASIC_AUTH
Content-Type: application/json
Host: api.fivetran.com
Content-Length: 73
{
"scope": {
"schema": [
"table1",
"table2"
]
}
}Responses
200
Successful response
404
Not found error
Successful response schema
code
stringrequired
Response status code
example:
message
stringrequired
Response status text
example:
{
"code": "Success",
"message": "Operation performed."
}