Skip to main content
POST /v1/tenants/{tenant_id}/bundle/read Returns the full definition of a named bundle, including its arguments and operations. Use this to inspect how a bundle is configured before running it.

Path Parameters

tenant_id
string
required
The tenant identifier. Use t1 for single-tenant deployments. Must match ^([a-zA-Z0-9_\-@\.:+]{1,128}|\*)$.

Request Body

name
string
required
The name of the bundle to retrieve.

Response

bundle
object
The bundle definition.

Example

curl --location --request POST 'localhost:3476/v1/tenants/{tenant_id}/bundle/read' \
--header 'Content-Type: application/json' \
--data-raw '{
    "name": "organization_created"
}'
Request body
{
  "name": "organization_created"
}
Response
{
  "bundle": {
    "name": "organization_created",
    "arguments": ["creatorID", "organizationID"],
    "operations": [
      {
        "relationships_write": [
          "organization:{{.organizationID}}#admin@user:{{.creatorID}}",
          "organization:{{.organizationID}}#manager@user:{{.creatorID}}"
        ],
        "attributes_write": [
          "organization:{{.organizationID}}$public|boolean:false"
        ]
      }
    ]
  }
}

Error Codes

HTTP StatusDescription
400Bad request — missing bundle name
401Unauthorized
404Tenant or bundle not found
429Rate limit exceeded
500Internal server error

Build docs developers (and LLMs) love