We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Skip to content
SendiMessage
Request a Line
iMessage API

The iMessage API for sending and receiving messages

Send iMessage programmatically through one clean REST API — with automatic SMS fallback where configured, incoming replies where enabled, dedicated lines, delivery tracking, and signed webhooks.

There is no official Apple iMessage API — here is what works

Apple does not offer a public iMessage API, and SendiMessage is not affiliated with Apple. What we provide is managed messaging infrastructure: dedicated lines where messages deliver over iMessage where supported, and over SMS where it is not. You integrate one API and one webhook contract; the routing, fallback, and delivery lifecycle are handled for you. Read why iMessage delivery is conditional for the honest details.

How it works

From request to conversation in three steps.

01

Request a line

Tell us your use case, market, and volume. We provision a dedicated messaging line and guide the integration — no self-serve signup, no shared numbers.

02

Send through one API

One POST request sends a message. The platform selects iMessage where supported and falls back to SMS where configured — your code stays the same.

03

React to events

Delivery statuses and incoming replies reach your systems as signed webhooks, so your CRM, store, or helpdesk always reflects the real conversation.

Send your first message

One request to send iMessage from your API.

POST https://api.sendimessage.com/v1/send-message — the same contract documented in the API documentation, in your language:

bash
curl --request POST \
  --url "https://api.sendimessage.com/v1/send-message" \
  --max-time 15 \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "X-API-Key: ${SENDIMESSAGE_API_KEY}" \
  --header "X-API-Secret: ${SENDIMESSAGE_API_SECRET}" \
  --data '{
  "number": "+15551234567",
  "content": "Hello from the API",
  "media_url": null,
  "status_callback": "https://example.com/callbacks/status",
  "line_handle": "line_example"
}'
What you get

Built for the whole delivery lifecycle.

iMessage where supported

Messages route over iMessage when the recipient can receive it — read receipts, rich replies, and the conversation experience customers expect.

Automatic SMS fallback

Where fallback is configured on your line, undeliverable iMessage traffic is re-sent as SMS automatically — one request, consistent delivery.

Incoming replies

On lines with incoming messaging enabled, customer replies arrive as signed webhooks and in the team inbox — real two-way conversations, not one-way blasts.

Dedicated lines

Every business gets its own provisioned messaging line — no shared pools, predictable sender identity, and a review-based onboarding.

Delivery tracking

Every message carries a status history — queued, sent, delivered, failed — available in the API and pushed to your webhook endpoint.

Integrations

Tested examples for your language and framework, plus CRM, e-commerce, and helpdesk integration guides with webhook events back to your systems.

FAQ

iMessage API questions, answered.

Is there an official Apple iMessage API?
No — Apple does not offer a public iMessage API for business messaging, and SendiMessage is not affiliated with or endorsed by Apple. SendiMessage provides dedicated managed messaging lines with one REST API: messages deliver over iMessage where supported, with automatic SMS fallback where configured.
Can I send iMessage from my own application?
Yes. You call one endpoint — POST /send-message — with the recipient number, the content, and your line handle. The API accepts the message, routes it, and reports every delivery status change back to your webhook endpoint.
What happens when a recipient cannot receive iMessage?
With SMS fallback configured on your line, the message is delivered as SMS instead, automatically. The status history records which channel actually delivered, so your system always knows what happened.
Can I receive replies to messages sent through the API?
Yes — on lines with incoming messaging enabled, replies are delivered to your systems as signed webhooks and are visible in the team inbox, so you can build real two-way conversations.
How much work is the integration?
It is a standard REST API with JSON request and response bodies — most teams send their first message with a few lines of code in curl, JavaScript, Python, PHP, or Go. Every line comes with direct integration support from our team.
How is the iMessage API priced?
Pricing is per active messaging line. Every line includes API access, delivery tracking, webhooks, and onboarding support — see the pricing page for details.

Start with a dedicated line.

Explore the iMessage API documentation for developers, the full API reference, iMessage API pricing, and integrations for your CRM, store, or helpdesk — or tell us about your use case and we will guide the integration.