Skip to main content
GET
/
v1
/
material-application-configs
/
{id}
Get a material application config
curl --request GET \
  --url https://api.cula.tech/tracking/v1/v1/material-application-configs/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "stc_01kqzcjrpyf27tgef1k5q27063",
  "active_version_id": "scv_01kqzcjrpyf27tgeg6k4kz2hyq",
  "site": {
    "id": "<string>",
    "external_id": "<string>"
  },
  "created_at": "2026-01-15T08:00:00Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.cula.tech/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API key passed as a Bearer token. Keys are scoped to one organisation and a set of permitted sites. Two keys per scope (primary + secondary) are issued to support zero-downtime rotation.

Authorization: Bearer <api-key>

Path Parameters

​
id
string
required

Cula-assigned resource ID in TypeID format (e.g. stp_01kqzcjrpxf27tge33jwvjhkff). Alternatively, pass your external ID prefixed with ext- (e.g. ext-MY-STEP-001). The ext- prefix is unambiguous because TypeIDs use _ separators and never start with ext-.

Response

Material application config.

A material application config. Points to its active version.

​
id
string
required

Config ID. Use this as config_id when creating material application step executions.

Example:

"stc_01kqzcjrpyf27tgef1k5q27063"

​
active_version_id
string
required

ID of the currently active version.

Example:

"scv_01kqzcjrpyf27tgeg6k4kz2hyq"

​
site
object
required

The site this config belongs to.

​
created_at
string<date-time>
required
Example:

"2026-01-15T08:00:00Z"