Retrieve a specific published version of an outgoing delivery config. The response includes the full data point configs, payload config, and selectable transport emission log configs inline.
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.
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>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-.
Config version ID.
Config version detail.
A published version of an outgoing delivery config with inline data point configs, payload config, and transport emission log configs.
Config version ID.
"dcv_01kqzcjrpyf27tgejmj16v1jjq"
Parent config ID.
"dlc_01kqzcjrpyf27tgehft3xhahn8"
Human-readable name of this config version.
"CO2 Outgoing Shipment"
When this version was published.
"2026-01-15T08:00:00Z"
Delivery-level data point configs. Use these id values as
config_id in the top-level data_points array when creating
a delivery.
Payload container config. Describes the data points expected
on each payload container in payload[].data_points.
Transport emission log configs that can be selected for
delivery legs via selected_emission_log_config_id.
ID of the next version in the chain. Null if this is the active (latest published) version.
null
Whether deliveries using this config can have more than one leg.
true
ID of the default transport emission log config. References
one of the items in selectable_transport_emission_log_configs.
Used when the leg omits selected_emission_log_config_id.
"elc_01kqzcjrpyf27tgekeyq3qzm7d"
JSON Schema (draft 2020-12) describing the expected request body shape for creating a runtime resource with this config version. The schema encodes which data points are required at each nesting level (delivery-level, leg-level, payload container-level). Partners can use this for client-side validation before sending requests. See Request body schema for details on how to use this field.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [
"config_id",
"issuing_site",
"legs",
"payload"
],
"properties": {
"data_points": {
"type": "array",
"description": "Delivery-level data points",
"x-required-config-ids": []
},
"legs": {
"type": "array",
"minItems": 1,
"items": {
"type": "object",
"required": ["sender_site", "receiver_site"],
"properties": {
"data_points": {
"type": "array",
"x-required-config-ids": []
}
}
}
},
"payload": {
"type": "array",
"minItems": 1,
"items": {
"type": "object",
"properties": {
"data_points": {
"type": "array",
"x-required-config-ids": [
"dpc_01kqzcjrpyf27tget3a94z1yhz",
"dpc_01kqzcjrpyf27tget5b05a2cbs"
]
}
}
}
}
}
}