LeadConduit uses HTTP Basic Authentication
with the username API and your API key as the password.
For example: API:1f1b96c9150d8050e858c043d543bb4eadae0e6f'
Return only events that were created after the one with this ID (exclusive) 24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
Return only events that were created before the one with this ID (exclusive) 24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
Return only events that were created at or after this time
Return only events that were created at or before this time
Stringified array of Rules to select matching events
An array of fields to include. Cannot be used with exclude.
An array of fields to exclude. Cannot be used with include.
The maximum number of events to return (maximum limit is 1000, default 100)
1 <= x <= 1000The results are sorted by date. Use asc to sort by oldest first or desc to sort by newest first. Defaults to desc.
OK
An event tracks what happened with a lead at a particular step in a flow. An event is a self-contained snapshot of the state of the lead at the time the lead visited the step. It contains a full copy of all lead data, along with all data that was appended before that step. Every event contains the below properties.
24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
The outcome of the event
success, failure, error The reason for a failure or error outcome
Recorded after a source submits a lead to a flow
source All data available at the time LeadConduit started processing this event
The number of milliseconds elapsed since epoch at the start of the step processing
The number of milliseconds elapsed since epoch at the end of the step processing
The number of milliseconds that elapsed while processing the lead
The number of milliseconds that LeadConduit spent waiting for all recipients to respond
The number of milliseconds of overhead that LeadConduit added while processing the step
The number of milliseconds that elapsed since the lead was submitted
The version of the lead handler
The schema version of the event
The ping limit configuration is defined in a flow on a source, or directly on the flow itself. The configuration controls the behavior of the ping limit by setting the maximum and the duration. The counter for a ping limit is kept as a standalone record which shares ping limit's ID.
The ping limit configuration is defined in a flow on a source, or directly on the flow itself. The configuration controls the behavior of the ping limit by setting the maximum and the duration. The counter for a ping limit is kept as a standalone record which shares ping limit's ID.
The time this event will be automatically deleted from LeadConduit (events are retained for 90 days)
The integration module ID configured for the source
The semantic version of the integration package
The acceptance criteria configured on the source when the lead was processed
The number of steps processed for this lead (>= 0 and <= total number of steps)
4
All data appended while handing the lead
The inbound HTTP request
The inbound HTTP response