---
title: "Lead Journey"
method: GET
path: "/api/v1/desk/leads/{lead_id}/journey"
tags: ["leads"]
---

# Lead Journey

`GET /api/v1/desk/leads/{lead_id}/journey`

## Request

- Base URL: `https://api.casaintelligence.com.au` (the document declares no server; this is the origin it was published from)
- URL: `https://api.casaintelligence.com.au/api/v1/desk/leads/{lead_id}/journey`
- Auth: none declared

Every property this lead's browsing session looked at, before or after they left their number.

The join key is the session, not the address on the lead row. That is what makes the ordering
irrelevant: the events keep arriving on the same session after the number is submitted, so a
person who asks for a call and then goes looking at three addresses shows all three, and a
person who looks first and asks after shows the same thing. Neither has to tell us anything.

Returns ``{linked, addresses, device, channel, first_seen, last_seen, events}``. ``linked`` is
false when no session could be tied to this lead, which is the honest answer for a lead created
before this link existed, or by a visitor whose browser refused session storage.

## Path parameters

- `lead_id` string, required

## Headers

- `x-desk-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/casaintelligence/apis/casa-intelligence-engine.md) · [All operations](https://skmtc.dev/casaintelligence/apis/casa-intelligence-engine/llms.txt) · [OpenAPI document](https://skmtc.dev/casaintelligence/apis/casa-intelligence-engine/revisions/71d711039de0?raw)