client.connectors.update_resource_acl(
"{connector_id}",
"{resource_id}",
request={
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
},
)
await client.connectors.updateResourceAcl({
id: "{connector_id}",
resourceId: "{resource_id}",
customInstructions: "These threads are incident retros. Extract root cause, impact and owner.",
});
curl -X PATCH 'https://api.hydradb.com/connectors/{id}/resources/{resource_id}' \
-H "Authorization: Bearer $HYDRADB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
}'
{
"connector_id": "{connector_id}",
"resource_id": "{resource_id}",
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner.",
"custom_instructions_updated": true
}
Connectors
Update Connector Resource
Change one resource’s instructions or ACL, leaving everything else as it is.
PATCH
/
connectors
/
{id}
/
resources
/
{resource_id}
client.connectors.update_resource_acl(
"{connector_id}",
"{resource_id}",
request={
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
},
)
await client.connectors.updateResourceAcl({
id: "{connector_id}",
resourceId: "{resource_id}",
customInstructions: "These threads are incident retros. Extract root cause, impact and owner.",
});
curl -X PATCH 'https://api.hydradb.com/connectors/{id}/resources/{resource_id}' \
-H "Authorization: Bearer $HYDRADB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
}'
{
"connector_id": "{connector_id}",
"resource_id": "{resource_id}",
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner.",
"custom_instructions_updated": true
}
Updates one configured resource in place. Send
The response includes
custom_instructions, acl, or both. At least one is required, and any field you omit is left unchanged.
client.connectors.update_resource_acl(
"{connector_id}",
"{resource_id}",
request={
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
},
)
await client.connectors.updateResourceAcl({
id: "{connector_id}",
resourceId: "{resource_id}",
customInstructions: "These threads are incident retros. Extract root cause, impact and owner.",
});
curl -X PATCH 'https://api.hydradb.com/connectors/{id}/resources/{resource_id}' \
-H "Authorization: Bearer $HYDRADB_API_KEY" \
-H "API-Version: 2" \
-H "Content-Type: application/json" \
-d '{
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner."
}'
{
"connector_id": "{connector_id}",
"resource_id": "{resource_id}",
"custom_instructions": "These threads are incident retros. Extract root cause, impact and owner.",
"custom_instructions_updated": true
}
custom_instructions and acl only when the request set them, showing the stored values.
resource_id in the path is the id from List Connector Resources, for example a Slack channel id or a Supabase schema.table name. URL-encode it if it contains spaces or other reserved characters.
custom_instructionsreplaces connector-level instructions for this resource. Send""to inherit the connector’s instructions again. Changes affect future syncs. See Custom ingestion instructions.aclchanges access immediately, including for already-synced sources. Use["__public__"]for public access or[]to deny everyone. An ACL captured from the provider may replace it on the next sync. See Query.
Errors
400: neither field was sent,custom_instructionsis over 4,000 characters, oraclis malformed. Nothing is changed.404: no connector with this id in your organization, or no configured resource with thisresource_idon it.
Related resources
- Update Connector: set the connector-level instructions these override
- Custom ingestion instructions: how connector and resource instructions combine
- List Connector Resources: read the stored values back
Authorizations
Path Parameters
Body
application/json
Resource settings to change
Response
OK
Was this page helpful?
