Update a connector
const url = 'http://127.0.0.1:8080/v1/connectors/example';const options = { method: 'PATCH', headers: { 'Deedglass-Version': '2026-10-01', Authorization: 'Bearer <token>', 'Content-Type': 'application/json' }, body: '{"description":"example","status":"active","config":{},"expected_config_hash":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url http://127.0.0.1:8080/v1/connectors/example \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Deedglass-Version: 2026-10-01' \ --data '{ "description": "example", "status": "active", "config": {}, "expected_config_hash": "example" }'Replaces description, status (active or disabled) or the whole config. With expected_config_hash, a config that changed meanwhile is 409 conflict. A change seals connector.updated; the next call uses the new config. An admin+ Console session or an org admin key.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The connector’s id (con_…) or its name.
Header Parameters
Section titled “Header Parameters”The API version (YYYY-MM-DD). Leave it out to use your org’s pinned version (public routes use the latest). An unknown version is 400 api_version_invalid.
Needed when the request uses a Console session (it changes state); without it the answer is 403 csrf_failed. Not sent with an API key.
Request Bodyrequired
Section titled “Request Bodyrequired”object
object
Responses
Section titled “Responses”The connector after the change.
object
The normalized config.
object
Sha256: of the normalized config’s JCS form.
object
Qualified:
A credential’s metadata. Never a value, never a digest of one.
object
The field names.
The last 4 characters of a token of 24 or more (…9f2c), the username of basic auth, or user@host:port/db of a DSN.
object
The admin deed of the change this answers.
Example
{ "object": "connector", "status": "active", "tools": [ { "object": "tool", "side_effect": "read", "levels": [ "L0" ] } ], "credentials": { "object": "credential", "kind": "bearer" }, "health": { "status": "unknown" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
default
Section titled “default”An error. Every error has this envelope; doc_url explains the code.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.