Upsert resource binding

PUT/v1/servers/{serverId}/bindings/{targetType}

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
serverIdpathstringYesResource ID
targetTypepathdatabase | auth | agent_runtimeYesResource binding target type
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
targetIdstringYes
aliasstringNo
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Binding updatedapplication/json
FieldTypeRequiredDescription
serverIdstringNoResource ID.
bindingobjectNo
binding.idstringNoUnique identifier.
binding.targetTypedatabase | auth | agent_runtimeNo
binding.targetIdstringNo
binding.aliasstringNo
binding.accessModestringNo
binding.metadataobjectNoFree-form metadata object.
bindingsobject[]No
bindings[].idstringNoUnique identifier.
bindings[].targetTypedatabase | auth | agent_runtimeNo
bindings[].targetIdstringNo
bindings[].aliasstringNo
bindings[].accessModestringNo
bindings[].metadataobjectNoFree-form metadata object.
Upsert resource binding
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow