curl -X PATCH 'https://api.hydradb.com/connectors/{id}' \
-H "Authorization: Bearer $HYDRA_DB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "Aurora was renamed to Nimbus in January 2025; they are the same product. Index all Aurora content under Nimbus.",
"sync_interval_seconds": 3600
}'
{
"connector_id": "{connector_id}",
"sync_interval_seconds": 3600,
"next_sync_at": "2026-06-01T13:00:00Z",
"min_sync_interval_seconds": 300,
"max_sync_interval_seconds": 604800,
"custom_instructions_updated": true
}
Update Connector
Change a connector’s instructions, sync interval or credentials in place.
curl -X PATCH 'https://api.hydradb.com/connectors/{id}' \
-H "Authorization: Bearer $HYDRA_DB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "Aurora was renamed to Nimbus in January 2025; they are the same product. Index all Aurora content under Nimbus.",
"sync_interval_seconds": 3600
}'
{
"connector_id": "{connector_id}",
"sync_interval_seconds": 3600,
"next_sync_at": "2026-06-01T13:00:00Z",
"min_sync_interval_seconds": 300,
"max_sync_interval_seconds": 604800,
"custom_instructions_updated": true
}
custom_instructionssets the connector-level ingestion instructions, used by every resource that has no instructions of its own. Send""to clear them. Up to 4,000 characters. They apply from the next sync; documents already synced are not processed again. See Custom Ingestion Instructions.sync_interval_secondssets how often scheduled syncs run. The allowed range depends on the provider and comes back in the response asmin_sync_interval_secondsandmax_sync_interval_seconds. Values outside it are rejected, and0resets to the provider default. The next sync is rescheduled right away, so a shorter interval takes effect immediately.credentialsreconnects the connector, for example after a token expired or was revoked. Send the provider’s full credential set, the same as on create. The connector keeps its id, resources and sync positions, and a reconnect-required state is cleared.
curl -X PATCH 'https://api.hydradb.com/connectors/{id}' \
-H "Authorization: Bearer $HYDRA_DB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "Aurora was renamed to Nimbus in January 2025; they are the same product. Index all Aurora content under Nimbus.",
"sync_interval_seconds": 3600
}'
{
"connector_id": "{connector_id}",
"sync_interval_seconds": 3600,
"next_sync_at": "2026-06-01T13:00:00Z",
"min_sync_interval_seconds": 300,
"max_sync_interval_seconds": 604800,
"custom_instructions_updated": true
}
custom_instructions_updated and credentials_updated are present when the request changed those fields. Sending {} changes nothing and returns the current interval and the allowed range.
Errors
400:custom_instructionsis over 4,000 characters, orsync_interval_secondsis outside the provider’s range. Nothing is changed.404: no connector with this id in your workspace.422:credentialsdoes not match the provider’scredential_schema.
Related Resources
- Update Connector Resource: instructions for one resource
- Custom Ingestion Instructions: what instructions do and how they combine
- Get Connector: read the stored settings back
Authorizations
API key sent as a Bearer token: "Bearer prefix.secret"
Path Parameters
Connector ID
"HydraDoc1234"
Body
Connector update request
Provider-specific credentials. Their shape is the provider's credential_schema from GET /connectors/providers?id=<provider>, for example {"access_token": "..."}.
Show child attributes
Show child attributes
{ "api_token": "xoxb-..." }
Ingestion and indexing instructions for every resource on this connector that has no instructions of its own. Omit to leave unchanged; "" clears. Up to 4000 characters, applied from the next sync.
How frequently the scheduler triggers incremental syncs, in seconds. Bounded per provider; send 0 or omit to use the provider default. Change it later with PATCH /connectors/{id}.
3600
Response
OK
Connector this resource belongs to.
"conn_abc123"
true when this request replaced the stored credentials and cleared any reconnect-required state.
true
true when this request set or cleared the connector-level custom_instructions. The change applies from the next sync.
true
Largest sync_interval_seconds this connector's provider allows.
604800
Smallest sync_interval_seconds this connector's provider allows. Values below it are rejected, never clamped.
300
RFC3339 timestamp when the next scheduled sync will run.
"2026-07-02T18:00:00Z"
How frequently the scheduler triggers incremental syncs, in seconds. Bounded per provider; send 0 or omit to use the provider default. Change it later with PATCH /connectors/{id}.
3600
Was this page helpful?
