Skip to main content
GET
/
v1
/
tracks
/
{trackId}
Get track details
curl --request GET \
  --url https://api.doozy.live/v1/tracks/{trackId} \
  --header 'x-api-key: <api-key>'
{
  "object": "track",
  "id": "wf_abc123",
  "name": "New Hire Onboarding",
  "description": "30-day onboarding journey for new employees",
  "state": "active",
  "trigger_type": "user_join",
  "step_count": 8,
  "allow_self_join": true,
  "created_at": "2026-01-15T10:30:00.000Z",
  "updated_at": "2026-01-20T14:00:00.000Z",
  "steps": [
    {
      "object": "step",
      "id": "step_abc123",
      "title": "Welcome Message",
      "order": 1,
      "type": "message",
      "message": "Welcome to the team! Here's what you need to know..."
    }
  ],
  "metrics": {
    "object": "track_metrics",
    "users_added_last_30_days": 25,
    "users_added_all_time": 145,
    "active_users": 30,
    "completed_users": 100
  }
}

Authorizations

​
x-api-key
string
header
required

API key for authentication. Generate keys in the Doozy dashboard.

Path Parameters

​
trackId
string
required

The unique identifier of the track

Minimum string length: 1
Example:

"wf_abc123"

Response

Track details with steps and metrics

​
object
enum<string>
required

Object type identifier

Available options:
track
Example:

"track"

​
id
string
required

Unique track identifier

Example:

"wf_abc123"

​
name
string
required

Track name

Example:

"New Hire Onboarding"

​
description
string | null
required

Track description

Example:

"30-day onboarding journey for new employees"

​
state
enum<string>
required

Current state of the track

Available options:
draft,
active,
paused,
archived
Example:

"active"

​
trigger_type
enum<string>
required

How users are added to the track

Available options:
user_join,
manual_user_trigger,
schedule,
work_anniversary,
added_by_another_workflow,
self_join
Example:

"user_join"

​
step_count
integer
required

Number of steps in the track

Example:

8

​
allow_self_join
boolean
required

Whether users can self-enroll in the track

Example:

true

​
created_at
string
required

When the track was created (ISO 8601 format)

Example:

"2026-01-15T10:30:00.000Z"

​
updated_at
string
required

When the track was last updated (ISO 8601 format)

Example:

"2026-01-20T14:00:00.000Z"

​
steps
object[]
required

Steps in the track

​
metrics
object
required

Enrollment and completion metrics