Resources, integrations, and bindings API

Create and control tenant Resources, inspect contracts, and manage scoped Resource or Credential assignments.

Resources

MethodPathPurpose
GET / POST/v1/namespaces/:namespace/resourcesList ?kind=... or create a configured Resource
GET / DELETE/v1/namespaces/:namespace/resources/:kind/:idRead or delete a tenant-managed Resource
GET/v1/namespaces/:namespace/resources/:kind/:id/controlRead control head
POST/v1/namespaces/:namespace/resources/:kind/:id/enableEnable with eventId and optional reason
POST/v1/namespaces/:namespace/resources/:kind/:id/disableDisable with eventId and optional reason

Platform catalog Resources are merged into list/read responses but tenants cannot mutate or delete them.

Resource contracts

MethodPathPurpose
GET / POST/v1/namespaces/:namespace/resource-contractsList or publish an immutable Resource contract
GET/v1/namespaces/:namespace/resource-contracts/:id/:version?hash=...Read one exact contract

Resource contracts describe the operations, schemas, effects, and capabilities an integration must provide. Use the Console workflow for installing or configuring an integration rather than depending on implementation internals.

Scoped assignments

MethodPathPurpose
GET / POST/v1/namespaces/:namespace/bindingsList visible assignments or create one
GET / DELETE/v1/namespaces/:namespace/bindings/:idRead or delete one assignment head
POST/v1/namespaces/:namespace/bindings/:id/promotePromote to a new target when expectedHeadSeq still matches
POST/v1/namespaces/:namespace/bindings/:id/enable, /disable, /revokeApply an idempotent lifecycle control
GET/v1/namespaces/:namespace/integrations[/:id]Read owner-filtered integration projections

Creation and promotion declare the logical key, owner, target class, exact target CRN, optional contract, and event identity. Customer/principal callers can see only assignments within their accepted ownership boundary. See Scoped bindings for resolution semantics.