Check iMessage Availability (Single Lead)
iMessage Availability
Check iMessage Availability (Single Lead)
Check if a specific lead is reachable via iMessage. REST endpoint in the Tuco AI iMessage API — bearer-token auth, JSON request/response, full schema and code.
GET
Check iMessage Availability (Single Lead)
Check iMessage availability for a single lead using their stored phone numbers and emails. Tuco checks every address on the lead (phone, email, altPhone1-3, altEmail1-3) and stops at the first one that is iMessage-capable. Updates the lead’s
The same status is written back to the lead, so you can also read it via the Leads API.
availabilityStatus field.
Authentication
Query parameters
The lead’s ID (MongoDB ObjectId).Example:
667f1f77bcf86cd799439012Example
Success response (200)
Always
true on a 200 response.The lead ID that was checked.
Whether the lead is reachable via iMessage.
One of:
"available"— at least one stored address supports iMessage"unavailable"— none of the stored addresses support iMessage"error"— the check failed (temporary issue)
GoHighLevel contact ID, if linked.
GoHighLevel location ID, if linked.
HubSpot portal ID, if linked.
HubSpot contact ID, if linked.
Error responses
| Status | When | Body |
|---|---|---|
400 | Missing id parameter | { "error": "Lead ID is required" } |
401 | Invalid or missing API key | { "error": "Unauthorized" } |
404 | Lead not found | { "error": "Lead not found" } |
429 | API rate limit exceeded (200 req/min) | { "error": "Rate limit exceeded" } |
429 | All lines hit daily cap (70/day/line) | { "error": "Daily availability check quota exhausted" } |
500 | Internal server error | { "error": "Internal server error" } |