Update Bulk Sync | Polytomic Docs

Updates an existing bulk sync’s top-level configuration.

Updating a bulk sync is a full replacement of the sync’s top-level configuration. Every field in the request body is written to the sync; any field you omit is cleared or reset to its default value.

To make a partial change — for example, toggling active or swapping a schedule — fetch the current sync with GET /api/bulk/syncs/{id}, modify the fields you want to change, and send the complete object back in the update request.

Updates to active, schedules, and policies take effect immediately. Changes to source or destination configuration take effect on the sync’s next execution.

Because omitted fields are reset to their defaults, the discovery and naming options behave the same as on create when left out:

automatically_add_new_objects resets to not enabling newly discovered source objects automatically.
automatically_add_new_fields resets to enabling newly discovered fields on already selected objects.
normalize_names resets to enabled.

Send the existing values explicitly if you want to preserve a non-default or non-empty setting, including schema and field selections.

📘 Updating schemas

Schema updates are not performed through this endpoint. Use the Update Bulk Sync Schemas endpoint to change a subset of schemas, or Update Bulk Sync Schema to replace a single schema’s configuration.

Updates an existing bulk sync's top-level configuration. Updating a bulk sync is a **full replacement** of the sync's top-level configuration. Every field in the request body is written to the sync; any field you omit is cleared or reset to its default value. To make a partial change — for example, toggling `active` or swapping a schedule — fetch the current sync with [`GET /api/bulk/syncs/{id}`](../../../../api-reference/bulk-sync/get), modify the fields you want to change, and send the complete object back in the update request. Updates to `active`, `schedules`, and `policies` take effect immediately. Changes to source or destination configuration take effect on the sync's next execution. Because omitted fields are reset to their defaults, the discovery and naming options behave the same as on create when left out: - `automatically_add_new_objects` resets to not enabling newly discovered source objects automatically. - `automatically_add_new_fields` resets to enabling newly discovered fields on already selected objects. - `normalize_names` resets to enabled. Send the existing values explicitly if you want to preserve a non-default or non-empty setting, including schema and field selections. > 📘 Updating schemas > > Schema updates are not performed through this endpoint. Use the > [Update Bulk Sync Schemas](../../../../api-reference/bulk-sync/schemas/patch) > endpoint to change a subset of schemas, or > [Update Bulk Sync Schema](../../../../api-reference/bulk-sync/schemas/update) > to replace a single schema's configuration.

Authentication

AuthorizationBearer

Bearer user API key

AuthorizationBasic

Basic organization-scoped API key

Path parameters

idstringRequiredformat: "uuid"

Unique identifier of the bulk sync to update.

Request

This endpoint expects an object.

default_scheduleobjectRequired

destination_configurationmap from strings to anyRequired

Destination-specific bulk sync configuration (e.g. output schema name, file format). The accepted keys depend on the destination connection type.

destination_connection_idstringRequiredformat: "uuid"

Unique identifier of the connection rows are written to.

modeenumRequired

Allowed values:

namestringRequired

Human-readable name for the bulk sync.

source_connection_idstringRequiredformat: "uuid"

Unique identifier of the connection rows are read from.

activeboolean or nullOptional

Whether the sync is active. Inactive syncs do not run on their schedule but can still be triggered manually.

additional_scheduleslist of objects or nullOptional

Additional bulk sync schedules. Schedule times are interpreted in UTC.

automatically_add_new_fieldsenumOptional

Allowed values:

automatically_add_new_objectsenumOptional

Allowed values:

concurrency_limitinteger or nullOptional

Override the default concurrency limit for this sync.

data_cutoff_timestampstring or nullOptionalformat: "date-time"

Global cutoff applied across schemas. Source records older than this timestamp are excluded from sync runs.

disable_record_timestampsboolean or nullOptionalDefaults to false

When true, Polytomic will not add its own timestamp columns to destination rows.

normalize_namesenumOptional

Allowed values:

organization_idstring or nullOptionalformat: "uuid"

Organization the sync belongs to. Only used by partner callers; normal callers are always scoped to their own organization.

policieslist of strings or nullOptional

Identifiers of permissions policies applied to the bulk sync.

resync_concurrency_limitinteger or nullOptional

Override the default resync concurrency limit for this sync.

schemaslist of strings or objects or nullOptional

List of schemas to sync; if omitted, all schemas will be selected for syncing.

source_configurationmap from strings to any or nullOptional

Source-specific bulk sync configuration (e.g. replication slot name, sync lookback). The accepted keys depend on the source connection type.

Response

dataobject

Errors

400

Bad Request Error

403

Forbidden Error

404

Not Found Error

500

Internal Server Error

Updates an existing bulk sync’s top-level configuration.

Updates to active, schedules, and policies take effect immediately. Changes to source or destination configuration take effect on the sync’s next execution.

Because omitted fields are reset to their defaults, the discovery and naming options behave the same as on create when left out:

automatically_add_new_objects resets to not enabling newly discovered source objects automatically.
automatically_add_new_fields resets to enabling newly discovered fields on already selected objects.
normalize_names resets to enabled.

Send the existing values explicitly if you want to preserve a non-default or non-empty setting, including schema and field selections.

📘 Updating schemas

Schema updates are not performed through this endpoint. Use the Update Bulk Sync Schemas endpoint to change a subset of schemas, or Update Bulk Sync Schema to replace a single schema’s configuration.

1	curl -X PUT https://app.polytomic.com/api/bulk/syncs/248df4b7-aa70-47b8-a036-33ac447e668d \
2	-H "X-Polytomic-Version: X-Polytomic-Version" \
3	-H "Authorization: Bearer <token>" \
4	-H "Content-Type: application/json" \
5	-d '{
6	"default_schedule": {
7	"frequency": "manual"
8	},
9	"destination_configuration": {
10	"schema": "my_schema"
11	},
12	"destination_connection_id": "248df4b7-aa70-47b8-a036-33ac447e668d",
13	"mode": "snapshot",
14	"name": "My Bulk Sync",
15	"source_connection_id": "248df4b7-aa70-47b8-a036-33ac447e668d"
16	}'

1	{
2	"data": {
3	"active": true,
4	"additional_schedules": [
5	{
6	"frequency": "weekly",
7	"created_at": "2023-04-25T12:00:00Z",
8	"created_by": {
9	"id": "12345678-1234-1234-1234-123456789012",
10	"name": "John Doe",
11	"type": "user"
12	},
13	"day_of_week": "monday",
14	"hour": "12",
15	"minute": "30",
16	"selective_mode": "nonincrementalFields",
17	"updated_at": "2023-04-25T12:00:00Z",
18	"updated_by": {
19	"id": "12345678-1234-1234-1234-123456789012",
20	"name": "John Doe",
21	"type": "user"
22	}
23	},
24	{
25	"frequency": "continuous",
26	"created_at": "2023-04-25T12:00:00Z",
27	"created_by": {
28	"id": "12345678-1234-1234-1234-123456789012",
29	"name": "John Doe",
30	"type": "user"
31	},
32	"selective_mode": "incrementalFields",
33	"updated_at": "2023-04-25T12:00:00Z",
34	"updated_by": {
35	"id": "12345678-1234-1234-1234-123456789012",
36	"name": "John Doe",
37	"type": "user"
38	}
39	}
40	],
41	"automatically_add_new_fields": "all",
42	"automatically_add_new_objects": "all",
43	"concurrency_limit": 50,
44	"created_at": "2024-01-15T09:30:00Z",
45	"created_by": {
46	"id": "12345678-1234-1234-1234-123456789012",
47	"name": "John Doe",
48	"type": "user"
49	},
50	"data_cutoff_timestamp": "2023-04-25T12:00:00Z",
51	"default_schedule": {
52	"frequency": "manual",
53	"created_at": "2024-01-15T09:30:00Z",
54	"created_by": {
55	"id": "12345678-1234-1234-1234-123456789012",
56	"name": "John Doe",
57	"type": "user"
58	},
59	"day_of_month": "1",
60	"day_of_week": "monday",
61	"hour": "12",
62	"id": "248df4b7-aa70-47b8-a036-33ac447e668d",
63	"minute": "30",
64	"month": "1",
65	"updated_at": "2024-01-15T09:30:00Z",
66	"updated_by": {
67	"id": "12345678-1234-1234-1234-123456789012",
68	"name": "John Doe",
69	"type": "user"
70	}
71	},
72	"destination_configuration": {
73	"schema": "my_schema"
74	},
75	"destination_connection_id": "248df4b7-aa70-47b8-a036-33ac447e668d",
76	"disable_record_timestamps": false,
77	"id": "248df4b7-aa70-47b8-a036-33ac447e668d",
78	"mode": "snapshot",
79	"name": "My Bulk Sync",
80	"normalize_names": "enabled",
81	"organization_id": "248df4b7-aa70-47b8-a036-33ac447e668d",
82	"policies": [
83	"248df4b7-aa70-47b8-a036-33ac447e668d"
84	],
85	"resync_concurrency_limit": 10,
86	"source_configuration": {
87	"replication_slot": "slot"
88	},
89	"source_connection_id": "248df4b7-aa70-47b8-a036-33ac447e668d",
90	"updated_at": "2024-01-15T09:30:00Z",
91	"updated_by": {
92	"id": "12345678-1234-1234-1234-123456789012",
93	"name": "John Doe",
94	"type": "user"
95	}
96	}
97	}

Authentication

Path parameters

Headers

Request

Response

Errors