Developer API

Ship iMessage. In minutes.

A REST API and real-time webhooks for sending iMessages programmatically. No private APIs. Fully compliant.

Last updated:

Read the Docs

Quick Start

One call. Delivered.

Send your first iMessage with a single POST request.

POST /v1/messages
curl -X POST https://api.tuco.ai/v1/messages \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d {
    "to": "+15550123456",
    "body": "Your table is ready!",
    "attachments": []
  }

Platform

Everything you need.

🌐

REST API

Send iMessages, manage contacts, and retrieve delivery status with simple HTTP calls. JSON in, JSON out.

🔔

Real-time Webhooks

Subscribe to message.received, message.failed, and call.incoming. Push data to your DB the instant it happens.

📦

Typed SDKs

First-class TypeScript support. Python and Go SDKs available. Autocomplete your way to production.

🔄

CRM Sync

Push reply state, delivery receipts, and opt-outs directly into HubSpot, Salesforce, or GoHighLevel in real time.

Why Tuco

Built for developers.

5-minute integration

Get your API key, send your first iMessage, and validate delivery -- all before your coffee gets cold.

No private APIs

Fully compliant infrastructure. No jailbreaks, no grey-market exploits. Enterprise-grade from day one.

99.9% uptime SLA

Built on redundant infrastructure with automatic failover. Your messages deliver when they need to.

Dedicated support

Engineering-to-engineering support. Talk to the people who built the API, not a ticket queue.

FAQ

Questions. Answered.

What can developers build with the Tuco AI iMessage API?

Developers can send iMessages programmatically, subscribe to webhooks, sync reply state into CRMs, and build custom workflows for sales, marketing, support, and operational messaging.

Does the API support webhooks and CRM-triggered automation?

Yes. The developer API supports webhook-driven automation so teams can trigger messages from product events, CRM changes, inbound leads, and custom backend workflows.

When should I use the developer API instead of a native integration?

Use the developer API when you need custom business logic, internal tooling, or integrations beyond HubSpot, Salesforce, and GoHighLevel. Native integrations are faster for standard CRM workflows.

Where should I start if I also need pricing and integrations?

Start with the docs for implementation details, then review the pricing page and integrations hub so engineering, RevOps, and buyers are aligned on rollout scope.

Start building today.

Get your API keys and send your first iMessage in under five minutes.

Read the DocsRequest a Demo
API PricingIntegrationsPlatformCompare Sendblue
Book a Demo3x reply rates