Get a specific delivery 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
"dlvcv_01kkw6g3ayad6f092rbkbjcaxq"
"dlvc_01kkygy9cxxqhhr93aw74aycbr"
Response
The ID of the delivery config version.
"dlvcv_01kkw6g3ayad6f092rbkbjcaxq"
The ID of the delivery config that this version belongs to.
"dlvc_01kkygy9cxxqhhr93aw74aycbr"
Human-readable name of the delivery config version.
"Corn Incoming Delivery"
Whether deliveries using this config can have more than one leg.
false
When this version was published.
"2026-01-15T08:00:00Z"
Whether the delivery and its payload are configured as one unified flow. When true, data_point_configs spans the whole flow (delivery and payload container) and creates take one flat data_points array. When false, payload_configs lists the container configs to describe payload containers against.
true
Data points that can be set on deliveries created from this config. For unified configs this spans the whole flow, including the payload container's data points.
Use data_point_configs (unified configs) or payload_configs instead.
Only present when unified is false: the container configs new payload containers are described against (via payload_containers on create).