Orgs
Orgs — 2 operations on https://api.hanzo.ai.
The REST reference for Orgs — 2 operations, generated from the OpenAPI document.
| Base URL | https://api.hanzo.ai |
| Operations | 2 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
orgs
Get lists the products an org has ENABLED — its own intent, which the console's paid-product sidebar reads to decide what to show.
GET /v1/orgs/{org}/entitlements
Get lists the products an org has ENABLED — its own intent, which the console's paid-product sidebar reads to decide what to show. It is distinct from what the org's plan ENTITLES it to (that is GET /v1/entitlements, resolved from commerce).
A caller may only read its OWN org's row; a platform super admin may read any.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
org | path | string | yes |
Post turns products on or off for an org and returns the enabled set afterwards.
POST /v1/orgs/{org}/entitlements
Post turns products on or off for an org and returns the enabled set afterwards.
A product may only be ENABLED if the org's plan already ENTITLES it, so enabling never spends new money — a product the plan does not grant answers 402 and the console routes that to an upgrade prompt. DISABLING is never gated. A platform super admin bypasses the plan check (operator comp/grant) and may target any org; everyone else may only change their own. Commerce unreachable is a 503, never an implicit yes.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
org | path | string | yes |
Request body — application/json (required)
| Field | Type | Required | Description |
|---|---|---|---|
add | string[] | — | Add is the product ids to turn ON. Each must already be an ACTIVE entitlement of the org's plan, unless the caller is a |
remove | string[] | — | Remove is the product ids to turn OFF. |
How is this guide?