BlueSender API

BlueSender bridges Apple Messages with CRM systems. A Mac running the BlueSender app monitors the local Messages database for incoming iMessages / SMS and forwards them to your CRM, while also receiving outbound messages from your CRM and sending them through Apple Messages.

This documentation covers the HTTP integration contract for third-party CRMs and tools that want to integrate with BlueSender.

How it fits together

• Your CRM speaks HTTP to the BlueSender backend in both directions:
  • Outbound (CRM → BlueSender): POST /crm/webhook to send a message through to the Mac.
  • Inbound (BlueSender → CRM): BlueSender calls your CRM API directly — POST /conversations/messages/inbound for inbound iMessages / SMS, and PUT /conversations/messages/{messageId}/status for status updates on previously-sent outbound messages. See Backend → CRM delivery for the request shapes.
• The BlueSender backend translates between HTTP (CRM-facing) and WebSocket (Mac-facing).
• The Mac client runs Apple Messages on behalf of a locationId, speaking WebSocket to the backend.

CRM integrators only need to implement the HTTP side. The WebSocket contract between backend and Mac is an internal protocol — CRMs do not connect to it directly.

Where to start

• New to BlueSender? Read the Quickstart.
• Wiring a CRM? Jump to HTTP Webhooks.
• Looking for a specific feature? See the Per-feature Guides.