Skip to main content
POST
Set a procedure version's connections
Replaces a version’s connection bindings with the complete ordered list in apiIntegrations ([] clears them), as Console’s binding editor does. Each entry names a vendorKey and one of that vendor’s registered connectionNames, with an optional host. The first entry that does not resolve is 400 bad_request, and the message names its index; nothing is written. Whether a connection’s hosts are in the version’s egress allowlist is not checked. Read the result with Diagnose a procedure version’s connection bindings.

Who may set connections

You need procedures:manage at the version’s home org unit; a missing version and one out of reach are the same 404 resource_missing. The change is audited (procedure_connections_set) with the prior and new targets and you as the actor.

Idempotency

With an Idempotency-Key, a same-key repeat within 24 hours returns the recorded result only while you still hold procedures:manage at the version’s home; otherwise 409 idempotency_result_unavailable.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Headers

Idempotency-Key
string

Optional logical intent key. A same-key retry within 24 hours returns the recorded result without writing again.

Required string length: 1 - 255

Path Parameters

procedureId
string
required

The procedure family's id (its slug).

Minimum string length: 1

Body

application/json
version
string
required

The semver version.

Minimum string length: 1
apiIntegrations
object[]
required

The complete ordered binding list; it replaces the stored one. [] clears it.

Response

Success

data
object
required
meta
object
required