Skip to main content
GET
GetLeadTimelineAPI mirrors the erdo_get_lead_timeline MCP tool.

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Path Parameters

datasetSlug
string
required
leadRef
string
required

Response

Success response

canonical_lead_id
string
context_columns
string[]

None of these columns is something the lead said: each is marked by the dataset's contract as bookkeeping, attribution, or a column the platform stamps itself, under whatever name the contract gave it. Read through partition, never directly.

dataset_id
string
dataset_slug
string
details
LeadDetail is one question a lead answered: the current answer and every · object[]

conversation, one entry per question with the answers it replaced.

emails
string[]
entries
TimelineEntry is one thing that happened with a lead, in any channel. · object[]
lead_reference
string
phones
string[]
reset_at
string<date-time>

row's arrival and the answers above begin there, because that is what the engine decides from; absent for a lead that was never reset.

row
object
timing
TimingFacts are the counts and clock readings a schedule rule needs, made by · object

the platform so "no response four days after the second email" is matched on numbers rather than on date arithmetic the model does.

unavailable
Unavailable names each source that could not be read and why. A source · object

listed here is unknown, never empty — the evaluation is told so.

undeliverable_emails
UndeliverableEmails is each of the lead's addresses that an earlier email · object

showed cannot take mail — it bounced, or the person reported it as spam — with what the provider said. Email to one of them is refused (channelRefusal): a second message to a dead mailbox reaches nobody and costs the development's sending reputation, and one to a person who reported us is mail they have already refused.