Get a specific material utilization config version
Authorizations
OAuth 2.0 client credentials. Exchange your client_id and client_secret for an access token scoped to the organisation that provides data access.
Headers
ID of the organisation the request operates on behalf of (e.g. org_...). Must be an organisation the API client has access to.
"org_01k83mfmhgchya944v86ryvhpq"
Path Parameters
"mutcv_01kbr6p08518pexf6rs9segz8j"
"mutc_01k16bap2kcz0asd2h2dkzz1xj"
Response
The ID of the config version.
"mutcv_01kbr6p08518pexf6rs9segz8j"
The ID of the config this version belongs to.
"mutc_01k16bap2kcz0asd2h2dkzz1xj"
Human-readable name of the config version.
"Soil Application"
When this version was published.
"2026-01-15T08:00:00Z"
Whether the utilization and its input containers are configured as one unified flow. When true, data_point_configs spans the whole flow (utilization step and input containers) and creates take one flat data_points array. When false, input_configs lists the container configs to describe input containers against.
true
Data points that can be set on utilizations created from this config. For unified configs this spans the whole flow, including the input containers' data points.
Only present when unified is false: the container configs new input containers are described against (via input_containers on create).