Skip to main content
POST
Activates one or more resources and sets sync options. This is the step between discovery and the first sync. You can call configure again at any time to add resources, change sub_tenant_id, or update metadata - the cursor is preserved on reconfigure.

Path parameters

Request body

Resource item fields

See Connectors - Overview for how these merge with system-generated fields.
configured is the count of resources successfully activated.

Authorizations

Authorization
string
header
required

API key sent as a Bearer token: "Bearer prefix.secret"

Path Parameters

id
string
required

Connector ID

Example:

"HydraDoc1234"

Body

application/json

Resource selection and sync options

resources
object[]
required

Resources to activate for this connector. Each item corresponds to one entry from the Discover endpoint.

Example:
backfill_chunk_interval_seconds
integer

Internal interval for async backfill paging.

Example:

86400

full_visibility_roles
string[]

FullVisibilityRoles names the HubSpot roles whose members can see every record (PRO-2036). Resolved to ids against the portal at configure time and stored on the account-wide resource row. A pointer so an omitted field keeps the current setting while an explicit [] clears it.

lookback_days
integer

How far back the first sync fetches historical data. Only applies to the initial sync — subsequent syncs are incremental from the last cursor.

Example:

30

table_configs
object[]

TableConfigs carries per-table replication settings for MOVEIT connectors whose tap reads a table_configs credential input (bigquery). Configure merges them into the stored credential bundle before the first sync, so the mode chosen at selection time governs every sync from the start. Optional; rejected for non-MOVEIT engines.

Response

OK

backfill
boolean
Example:

true

configured
integer
Example:

1

connector_id
string

Connector this resource belongs to.

Example:

"conn_abc123"

first_sync_at
string

FirstSyncAt/Message state the timing expectation: whether the first sync is already running (configure triggers one) or when the scheduled one runs, so clients stop inventing their own copy (PRO-1565).

message
string

Human-readable result message.

Example:

"Success"

meta
object
warnings
string[]

Warnings names resources that were saved but produced nothing when probed. They are valid — the user may know a table is empty and expect it to fill — so they are not rejected, but they are the case that is otherwise indistinguishable from success at every layer, so they are never saved silently either.