Integration builder

Build your SendiMessage integration

Choose your existing workflow and see how SendiMessage fits between your application and customer messaging.

Architecture demo — no production configuration is changed.

Every SendiMessage integration follows the same shape: your application calls one REST API to send a message through a dedicated managed line. Where incoming messaging is enabled, customer replies are delivered back to your application as signed webhook events — so your system stays the source of truth while SendiMessage operates the messaging infrastructure underneath it.

Outbound delivery can route over iMessage where the recipient and line support it, with SMS fallback where configured — fallback behavior depends on line configuration and destination support, never guaranteed. The configurator below lets you see how these pieces connect for your specific workflow.

What system will connect to SendiMessage?

What messaging direction do you need?

How should outbound delivery work?

Which events does your application need?

Select all that apply.

How many messaging lines does this workflow require?

Line strategy is reviewed during onboarding.

Live architecture

Your application

SendiMessage API

REST API

Managed Messaging Lines

Customer

Your configuration

Source system: Your application
Messaging: Not selected
Delivery: Not selected
Events: Not selected
Lines: Not selected

What your system does

Decides when to send a message
Calls the SendiMessage API
Owns the business logic and records

What SendiMessage manages

The messaging line
The message transport workflow (routing, delivery)

What returns to your system

Nothing yet — select events above

Your application owns

Business logic
Customer/CRM records
Scheduling
AI decisions

SendiMessage manages

Messaging API
Managed lines
Messaging workflow
Webhooks / events

POST https://api.sendimessage.com/v1/send-message

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": "+15550100123",
  "content": "Hello from the API",
  "media_url": null,
  "status_callback": "https://example.com/callbacks/status",
  "line_handle": "8eb3ecaf-6487-485d-b01c-b18bdcb57180"
}'

Ready to try this with a real line?

This is an architecture pattern, not a production configuration — nothing here is saved to an account.

Build an API request →