Analyze multi-step transition paths

curl --request POST \
  --url https://api.mixpeek.com/v1/taxonomies/{taxonomy_id}/analytics/paths \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "collection_id": "<string>",
  "taxonomy_id": "<string>",
  "from_step": "<string>",
  "to_step": "<string>",
  "max_path_length": 10,
  "min_support": 5,
  "max_window_days": 123,
  "filters": {}
}
'

{
  "from_step": "<string>",
  "to_step": "<string>",
  "total_sequences": 123,
  "completed_sequences": 123,
  "completion_rate": 0.5,
  "paths": [
    {
      "path": [
        "<string>"
      ],
      "count": 1,
      "percentage": 50,
      "avg_duration_sec": 123
    }
  ]
}

Analytics

Analyze multi-step transition paths

Discover the most common multi-step paths documents take between two taxonomy steps.

Unlike the /transitions endpoint which only analyzes direct A→B transitions, this endpoint reveals the intermediate steps documents actually take.

Use Cases

Email Thread Analysis:

Question: What paths do emails take from “inquiry” to “closed_won”?
Discover: Some go inquiry → followup → proposal → closed_won
Discover: Others skip steps: inquiry → proposal → closed_won
Discover: Fast track: inquiry → closed_won

Content Editorial Paths:

Question: Common paths from “draft” to “published”?
Discover: draft → review → edit → review → published
Discover: draft → review → published (expedited)
Discover: Paths that loop back (draft → review → draft → review)

Compliance Resolution Paths:

Question: How do violations get resolved?
Discover: violation → investigated → remediated → resolved
Discover: violation → false_positive → closed
Discover: Escalation paths: violation → escalated → legal_review → resolved

Requirements

Taxonomy must have step_analytics configured
Collection must contain documents with timestamp and sequence_id fields

Returns

Completion Metrics:

total_sequences: Sequences starting at from_step
completed_sequences: Number reaching to_step
completion_rate: Percentage that completed

Paths (sorted by frequency):

path: Ordered sequence of steps
count: Number of sequences following this path
percentage: Percentage of completing sequences
avg_duration_sec: Average time for this path

Example Request

{
    "collection_id": "col_emails",
    "taxonomy_id": "tax_sales_stages",
    "from_step": "inquiry",
    "to_step": "closed_won",
    "max_path_length": 10,
    "min_support": 5
}

Example Response

{
    "from_step": "inquiry",
    "to_step": "closed_won",
    "total_sequences": 1000,
    "completed_sequences": 350,
    "completion_rate": 0.35,
    "paths": [
        {
            "path": ["inquiry", "followup", "proposal", "closed_won"],
            "count": 120,
            "percentage": 34.3,
            "avg_duration_sec": 604800.0
        },
        {
            "path": ["inquiry", "proposal", "closed_won"],
            "count": 90,
            "percentage": 25.7,
            "avg_duration_sec": 432000.0
        },
        {
            "path": ["inquiry", "closed_won"],
            "count": 70,
            "percentage": 20.0,
            "avg_duration_sec": 172800.0
        }
    ]
}

Path Interpretation

Length Analysis:

Shorter paths indicate efficient progression
Longer paths may indicate complexity or bottlenecks
Loops (repeated steps) indicate rework or revisions

Duration Analysis:

Compare avg_duration_sec across paths
Shorter paths may not always be faster
Identify optimization opportunities

Frequency Analysis:

High-percentage paths are “happy paths”
Low-percentage paths may be edge cases or exceptions
Missing expected paths indicate drop-off points

POST

taxonomies

{taxonomy_id}

analytics

paths

Analyze multi-step transition paths

curl --request POST \
  --url https://api.mixpeek.com/v1/taxonomies/{taxonomy_id}/analytics/paths \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "collection_id": "<string>",
  "taxonomy_id": "<string>",
  "from_step": "<string>",
  "to_step": "<string>",
  "max_path_length": 10,
  "min_support": 5,
  "max_window_days": 123,
  "filters": {}
}
'

{
  "from_step": "<string>",
  "to_step": "<string>",
  "total_sequences": 123,
  "completed_sequences": 123,
  "completion_rate": 0.5,
  "paths": [
    {
      "path": [
        "<string>"
      ],
      "count": 1,
      "percentage": 50,
      "avg_duration_sec": 123
    }
  ]
}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

taxonomy_id

string

required

Body

application/json

API request model for multi-step path analysis.

Discovers the most common sequences of intermediate steps documents take when progressing from from_step to to_step.

Unlike the transitions endpoint which only analyzes direct A→B progressions, this endpoint reveals the actual paths taken (e.g., A → X → Y → B).

Example: json { "collection_id": "col_emails", "taxonomy_id": "tax_sales_stages", "from_step": "inquiry", "to_step": "closed_won", "max_path_length": 10, "min_support": 5 }

Response includes: - Most common paths sorted by frequency - Count and percentage for each path - Average duration per path

collection_id

string

required

Collection to analyze

taxonomy_id

string

required

Taxonomy ID

from_step

string

required

Starting step

to_step

string

required

Ending step

max_path_length

integer

default:10

Maximum number of steps in a path

Required range: 2 <= x <= 20

min_support

integer

default:5

Minimum sequences required to include a path

Required range: x >= 1

max_window_days

integer | null

Maximum duration for path completion (in days)

filters

Filters · object | null

Optional event filters

Response

Successful Response

API response model for multi-step path analysis.

Contains discovered transition paths with frequency and duration statistics.

Example Response: json { "from_step": "inquiry", "to_step": "closed_won", "total_sequences": 1000, "completed_sequences": 350, "completion_rate": 0.35, "paths": [ { "path": ["inquiry", "followup", "proposal", "closed_won"], "count": 120, "percentage": 34.3, "avg_duration_sec": 604800.0 }, { "path": ["inquiry", "proposal", "closed_won"], "count": 90, "percentage": 25.7, "avg_duration_sec": 432000.0 }, { "path": ["inquiry", "closed_won"], "count": 70, "percentage": 20.0, "avg_duration_sec": 172800.0 } ] }

from_step

string

required

to_step

string

required

total_sequences

integer

required

Total sequences that started at from_step

completed_sequences

integer

required

Number of sequences that reached to_step

completion_rate

number

required

Percentage that completed the path

Required range: 0 <= x <= 1

paths

TransitionPath · object[]

required

List of paths sorted by frequency (most common first)

Maximum array length: 100

Show child attributes

Compute step transition analytics Create Cluster