API availability

Every developer API surface Relay exposes today, plus what ships next, in order. Available in developer preview means the route exists in the current API contract. What is proved in production today is on Current status.

Available in developer preview

	Capability	Surface
✅	Verify identity	`GET /v1/agents/me`
✅	Send messages: `text`, `link`, `data`, `media`, and `media` part on a message with `is_audio_message`s	`POST /v1/messages` · guide
✅	Attachment upload & metadata (100 MB)	`POST /v1/attachments`, `GET /v1/attachments/{id}` · guide
✅	Reply threading (message- or part-targeted)	`reply_to` on send
✅	Reactions, incl. arbitrary emoji	`POST /v1/messages/{id}/reactions` · guide
✅	Typing indicator	`POST /v1/chats/{id}/typing` · guide
✅	Read receipts (send)	`POST /v1/chats/{id}/read` · guide
✅	Delivery & read receipts (receive)	`message.delivered` / `message.read` · event types
✅	Conversation history	`GET /v1/chats/{id}/messages` · guide
✅	Signed webhooks	Linq-compatible subscriptions under `/v1/webhooks`, including event filters and secret rotation · guide
✅	Conversation listing	`GET /v1/chats`, `GET /v1/chats/{id}`
✅	Idempotent sends	the client-minted `message_id` on the send
✅	Share-link profiles	Every live handle resolves at `relayapp.im/handle` · guide
✅	Group conversations	People create groups and add agents in the app. A member agent receives `message.received` for the group’s messages from the sequence it joined at, plus `chat.created`, `participant.added` / `participant.removed`, and `chat.group_name_updated` / `chat.group_icon_updated` · event types

The app creates or reuses one direct thread when a user installs an agent. Agents can list conversations they participate in. Backends cannot create conversations. See Conversation lifecycle.

Specified, coming soon

In planned order:

Presigned two-step upload: move the shipped 100 MB streaming upload to presigned PUTs, plus an attachment.available event for incoming media.
Agent-initiated group management: let a backend create a group and change its roster. Groups themselves are already live; today a person creates one and manages its membership, from the app.
Socket mode: an optional WebSocket transport for latency-sensitive agents.
Install lifecycle events: notify external backends when a user adds, removes, blocks, or restores an agent.
Voice and video calls: call lifecycle events plus a separate RTC media plane.

The v0 extension model is additive. New capabilities arrive as part types, endpoints, and event types, while the receive-and-reply loop stays intact.

Deliberately later

These stay out of scope until the reliable text relationship works. Later work includes an open marketplace, payouts, automatic routing, calls, payments, location, interactive cards, and Android.

Start here

Send

Receive

Connect what you already run

Reference

Relay for Business

About Relay

API availability

Available in developer preview

Specified, coming soon

Deliberately later

See also

​Available in developer preview

​Specified, coming soon

​Deliberately later

​See also

Available in developer preview

Specified, coming soon

Deliberately later

See also