Skip to main content
POST
Create a reusable choice catalogue.

Authorizations

Authorization
string
header
required

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

application/json

The definition for a reusable choice catalog.

id
string
required

A unique catalog ID containing 1–128 letters, numbers, ., _, or -.

Pattern: ^[A-Za-z0-9._-]{1,128}$
Example:

"support-actions"

model
string
required

The model used when this catalog is referenced by a decision.

Example:

"goldenfish-g1"

choices
string[]
required

The 2–300 unique, non-empty outcomes accepted by this catalog.

Required array length: 2 - 300 elements
Minimum string length: 1
version
string

An application-defined version label for change tracking.

Example:

"20261011.120000"

visibility
enum<string>
default:private

Whether the catalog is private to the caller or public in the deployment.

Available options:
private,
public

Response

Catalogue created.

A reusable choice catalog returned by the catalog endpoints.

id
string
required

The catalog identifier used in decision requests.

Example:

"support-actions"

object
any
required

Always catalog for this response object.

model
string
required

The model associated with the catalog.

Example:

"goldenfish-g1"

choices
string[]
required

The catalog's current valid outcomes.

visibility
enum<string>
required

The catalog's visibility in the deployment.

Available options:
private,
public
version
string

The version label supplied when the catalog was created.