Skip to main content

Guides

Send a message as System or as a specific agent​

Outbound message endpoints accept two optional attribution overrides:

  • as_system: true — the message appears as System (no read receipts).
  • from_user_id: "<agent_id>" — attribute the message to a specific agent/owner.
# As System
curl -X POST https://api.relasiu.com/api/public/v1/messages/text \
  -H "Authorization: Bearer ru_live_<id>.<secret>" \
  -H "Content-Type: application/json" \
  -d '{"client_request_id":"a1","conversation_id":"<id>","text":"Ticket resolved","as_system":true}'

# On behalf of an agent
curl -X POST https://api.relasiu.com/api/public/v1/messages/text \
  -H "Authorization: Bearer ru_live_<id>.<secret>" \
  -H "Content-Type: application/json" \
  -d '{"client_request_id":"a2","conversation_id":"<id>","text":"Hi!","from_user_id":"<agent_id>"}'

If neither is set, the message is attributed to the key's creator. as_system wins if both are sent. The same fields work as form fields on the media endpoints (/messages/image, /audio, /video, /document).

Sync incoming messages to your CRM​

  1. Create a webhook endpoint subscribed to message.created (or all events).
  2. On each delivery, verify the signature.
  3. Dedupe on X-Relasi-Webhook-Id, then upsert into your CRM.

Keep a contact in sync​

Listen for contact.created and contact.updated, or pull on demand:

curl "https://api.relasiu.com/api/public/v1/contacts?search=jane@example.com" \
  -H "Authorization: Bearer ru_live_<id>.<secret>"