Creates a new bulk sync.
Bulk syncs are used for the ELT pattern (Extract, Load, and Transform), where you want to sync un-transformed data to your data warehouses, databases, or cloud storage buckets like S3.
All of the functionality described in the product documentation is configurable via the API.
Sample code examples:
The destination_configuration is integration-specific configuration for the
selected bulk sync destination. This includes settings such as the output schema
and is required when creating a new sync.
The source_configuration is optional. It allows configuration for how
Polytomic reads data from the source connection. This will not be available for
integrations that do not support additional configuration.
Consult the connection configurations to see configurations for particular integrations (for example, here is the available source configuration for the PostgreSQL bulk sync source).
If schemas is omitted, the sync is created with all available source schemas
selected. Pass schemas explicitly if you want the initial sync to include
only a subset of tables or objects.
Schedule times are interpreted in UTC.
When omitted, automatic discovery defaults are conservative:
automatically_add_new_objects defaults to not enabling newly discovered
source objects automatically.automatically_add_new_fields defaults to enabling newly discovered fields
on already selected objects.normalize_names defaults to enabled.Basic organization-scoped API key
Destination-specific bulk sync configuration (e.g. output schema name, file format). The accepted keys depend on the destination connection type.
Human-readable name for the bulk sync.
Organization the sync is created in. Only used by partner callers; normal callers always create syncs in their own organization.
List of schemas to sync; if omitted, all schemas will be selected for syncing.
Source-specific bulk sync configuration (e.g. replication slot name, sync lookback). The accepted keys depend on the source connection type.