Check Replies
Replies
Check Replies
Get replies for a lead or campaign — who replied, what they said, and the conversation context. REST endpoint in the Tuco AI iMessage API — bearer-token auth.
GET
Check Replies
Use this endpoint to check if a specific lead has replied, or to list all leads who replied (optionally scoped to a campaign). Returns the reply text, up to 10 recent replies from the lead, and up to 10 outbound messages you sent them.
Authentication
Query parameters
Replies from this lead only (valid ObjectId; returns 404 if lead not found).
Restrict to leads who replied and are in this campaign.
Filter by reply sender email.
Filter by reply sender phone (E.164 or normalized).
Restrict to replies received on this Tuco line (24-char ObjectId hex). Returns
400 if malformed.Inclusive ISO 8601 UTC lower bound on the reply timestamp (e.g.
2026-06-01T00:00:00Z). Returns 400 if unparseable or greater than dateTo.Inclusive ISO 8601 UTC upper bound on the reply timestamp.
Page number.
Results per page (max 100).
Examples
Success response (200)
Reply fields
Lead who replied.
ID of the most recent reply message.
The reply text (e.g. “Stop”, “Interested!”, “Call me tomorrow”).
ISO 8601 timestamp of the most recent reply.
Lead’s phone number.
Lead’s email address.
Lead’s display name.
true when the lead’s newest inbound is newer than your newest outbound to them (no outbound on record → true). Any follow-up you send after their reply — including AI copilot auto-replies — flips it back to false. With campaignId set, outbounds are scoped to that campaign, so this reads as “replied since the campaign’s last message”.Always
true for a returned row — leads who never replied have no row. Included so this endpoint and the GHL Check for Replies action expose the same field names; branch on it when an auto-responder makes hasReplied flip to false within seconds.