v1
latestOpenAPI 3.0.32026-08-06138294578.6 KBUpdate Bulk Sync Schema
Replaces the configuration of a single schema on a bulk sync.
This is a full replacement: every field in the request body is written to the schema, and any field you omit is cleared or reset to its default. Fetch the current configuration with GET /api/bulk/syncs/{id}/schemas/{schema_id} first if you want to preserve existing settings while changing only a subset.
Omitting fields enables all available fields on the schema. To control which fields are enabled, include the fields array with explicit enabled values.
📘 To update multiple schemas in a single request without affecting others, use the partial-update endpoint PATCH /api/bulk/syncs/{id}/schemas instead.
Path parameters
Unique identifier of the bulk sync.
Unique identifier of the bulk sync.
Source-side schema identifier.
Source-side schema identifier.
Headers
Request body
Example request
{
"data_cutoff_timestamp": "2023-04-25T12:00:00Z",
"enabled": true,
"fields": [
{
"enabled": true,
"id": "email",
"user_output_name": "my_email"
}
],
"filters": [
{
"field_id": "field1",
"value": "value"
}
],
"partition_key": "email",
"tracking_field": "updated_at",
"user_output_name": "my_contact"
}Response
OK
Example response
{
"data": {
"data_cutoff_timestamp": "2023-04-25T12:00:00Z",
"enabled": true,
"fields": [
{
"enabled": true,
"id": "email",
"output_name": "email",
"user_output_name": "my_email"
}
],
"filters": [
{
"field_id": "field1",
"value": "value"
}
],
"id": "Contact",
"output_name": "contact",
"partition_key": "email",
"tracking_field": "updated_at",
"user_output_name": "my_contact"
}
}