Skip to main content
Pillar 2 of 3

Direct messages and comments arrive on a single message resource with one shape, and replies go back out through the same call.

Live on Facebook and Instagram

​
Coverage today

The inbox currently covers Facebook and Instagram. Support for the remaining networks is in build behind the same resource, so adding them will not change the shape of your code.
Do not build against the inbox for a network that is not listed above. Publishing is available on every network; the inbox is not.

​
The model

One message shape

A Facebook direct message and an Instagram comment arrive as the same object, with the same author, thread and timestamp fields.

Reply through the same resource

Replies are posted back into a thread with one call. Threading and per-network reply rules are applied for you.

Read state per thread

Unread state is tracked per conversation, so two agents working the same queue never answer the same message twice.

Author identity

The sender is resolved to a stable identifier where the network provides one, so repeat conversations can be linked.

​
Message kinds

Endpoint reference for the inbox is not in these docs yet. The only endpoint currently documented and playground-backed is GET /v1/profiles.