Concepts

Sub-labels

One key for a master label and every sub-label below it.

On this page

Allow a key to act for sub-labels
Name the sub-label on each call

A master label, or a white label running sub-labels, can drive all of them from one system with one key.

Allow a key to act for sub-labels#

An owner or admin turns on Sub-labels on the key in Workspace › API, with an authenticator code. GET /organizations then lists every organization the key can act for: its own, and the sub-labels below it where the key's member has access.

Name the sub-label on each call#

Send the sub-label's id in the Stillmore-Organization header:

curl https://api.stillmoregroup.com/api/v1/releases \
  -H "Authorization: Bearer $STILLMORE_API_KEY" \
  -H "Stillmore-Organization: <sub-label id>"

Ids, lists, permissions, review and events are then the sub-label's. The request log, usage and the rate limit stay with the key's organization.

Answer	Why
`403 SUB_LABELS_NOT_ALLOWED`	The key may not act for sub-labels; turn it on for the key
`403 SUB_LABEL_NOT_ALLOWED`	That organization is not below the key's, or the key's member can't open it
`400 INVALID_ORGANIZATION_HEADER`	The header isn't an organization id from `GET /organizations`