Skip to main content
POST
Endorse a change request

Authorizations

Authorization
string
header
required

murmur API key: mur_<key_id>.

Path Parameters

id
string
required

The change-request id to endorse (e.g. "cr-a1b2c3").

Body

application/json

EndorseChangeRequest adds the caller to a change-request's endorser set (idempotent — re-endorsing is a no-op). The endorser identity is stamped server-side from the authenticated caller (a Principal, or an AgentId for an agent-runtime caller), never read from the request. Allowed only while the change-request is non-terminal (PENDING/APPROVED). Gated by change-request.endorse AND {target_kind}.read on the target — strictly below the propose (create) and approve (target-write) permissions.

tenant
object

Tenant identifies an organization within a provider. It is the unit of multi-tenant scoping — all resources (agents, pools, VMs) belong to exactly one tenant.

Response

A successful response.

changeRequest
object

CatalogChangeRequest wraps a proposed change to ANY catalog resource and gates it behind an approval. It is generic over catalog Kind: target_kind names the kind, proposed_payload is the full proposed value for that kind, and apply reuses the same write path SetResource uses. Recipe is one possible target_kind, not a special case.