Skip to main content
GET
/
delivery-configs
/
{id}
Get a delivery config
curl --request GET \
  --url https://api.cula.tech/tracking/v1/delivery-configs/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Cula-Org-Id: <cula-org-id>'
{
  "id": "dlc_01kqzcjrpyf27tgegxm6bxfdhb",
  "active_version_id": "dcv_01kqzcjrpyf27tgej0x1ke3msk",
  "site": {
    "id": "<string>",
    "external_id": "<string>"
  },
  "direction": "incoming",
  "type": "implicit",
  "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

OAuth2 client credentials flow. Exchange your client_id and client_secret for a short-lived access token, then pass it as a Bearer token in the Authorization header.

Headers

​
Cula-Org-Id
string
required

Organisation ID that scopes this request. The authenticated consumer must be authorized for this organisation. Omitting this header returns 400; passing an unauthorised org returns 403.

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

Delivery config.

A delivery config. Points to its active version. The direction and type are fixed for the lifetime of the config — deliveries created from this config inherit them.

​
id
string
required

Config ID. Use this as config_id when creating deliveries.

Example:

"dlc_01kqzcjrpyf27tgegxm6bxfdhb"

​
active_version_id
string
required

ID of the currently active version.

Example:

"dcv_01kqzcjrpyf27tgej0x1ke3msk"

​
site
object
required

The site that owns this config. For incoming configs this is the receiving site; for outgoing configs this is the sending site.

​
direction
enum<string>
required

Direction of deliveries created from this config relative to the owning site. For incoming, the last leg's receiver_site must equal site. For outgoing, the first leg's sender_site must equal site.

Available options:
incoming,
outgoing
Example:

"incoming"

​
type
enum<string>
required

How the delivery determines its payload containers. The server materializes payload containers from the config. Inspect the config version's payload_config.data_point_configs[] to see which payload data point values are expected.

Available options:
implicit
Example:

"implicit"

​
created_at
string<date-time>
required
Example:

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