Enable a disabled provider connection again
The operator (installation.settings.manage, the workspace owner), signed in; an API key is 403 whatever its scopes. Brings a disabled connection back: ceilings over it match it again once the settings are read again (a reference to the deployment that does not resolve leaves it unresolved). It is refused with 409 not_disabled when the row is in use, 409 definition_active when another connection in use is, or was, exactly what this one is (disable that one first), and 409 needs_value when its stored value is gone (disabling keeps it, so this is rare). The destination never changes. Writes an enable_connection receipt.
Auth: cookie session only; no scope. Idempotency-Key: ignored.
cookieSession__Host-werft_session<token>For the web console: the browser session cookie set by POST /v1/auth/login. It holds the scopes of the user's workspace role (owner: all; admin and member: all but sessions:recover). Requests other than GET must also send X-Requested-With: werft-web.
id*stringThe model connection's id.
1 <= lengthX-Requested-With?"werft-web"Required with a cookie session: the literal werft-web.
"werft-web"The entry's id and the change's receipt.
application/json- response
id*string1 <= lengthreceipt_id*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidcurl -X POST 'https://example.com/v1/installation/settings/connections/string/enable'{ "id": "anthropic-console", "receipt_id": "019a0000-0000-7000-8000-0000000000f3"}