Create a reusable choice catalogue.
Creates a named catalog that can be referenced by ID from future decision requests. Catalog IDs are unique within the caller’s namespace. Catalog writes require a bearer API key.
Authorizations
Use a bearer key beginning with gf_live_... for protected catalog operations. Keep keys server-side. Aspas Labs does not currently expose a self-service dashboard or key-management page.
Body
The definition for a reusable choice catalog.
A unique catalog ID containing 1–128 letters, numbers, ., _, or -.
^[A-Za-z0-9._-]{1,128}$"support-actions"
The model used when this catalog is referenced by a decision.
"goldenfish-g1"
The 2–300 unique, non-empty outcomes accepted by this catalog.
2 - 300 elements1An application-defined version label for change tracking.
"20261011.120000"
Whether the catalog is private to the caller or public in the deployment.
private, public Response
Catalogue created.
A reusable choice catalog returned by the catalog endpoints.
The catalog identifier used in decision requests.
"support-actions"
Always catalog for this response object.
The model associated with the catalog.
"goldenfish-g1"
The catalog's current valid outcomes.
The catalog's visibility in the deployment.
private, public The version label supplied when the catalog was created.