Skip to main content
Direct Messages (DMs) in the Community API are moving from conversation-level to message-level interactions. This affects how you retrieve messages, read message content, and reply to users across all platforms.
Comment-based interactions (Facebook, Instagram, TikTok, YouTube) are not affected.
Endpoints: GET /community_interactions, GET /conversations/{conversation_id}, POST|PATCH /conversations/{conversation_id}/messages, PATCH /messages/{id} Action Required: Update endpoints, field references, and filters Impact Level: Breaking Change

​
Required Action

​
Update Field References

GET /community_interactions now returns one result per message instead of per conversation. For example, if a user sends 3 messages, they will appear as 3 separate results instead of 1 thread. Read message content directly from text.

​
Update Conversation ID References

Existing conversation IDs will be migrated as part of this change. Old conversation IDs will not work with the new endpoints after the effective date.

​
Update Endpoints

The new endpoints apply to all platforms. Platform-specific endpoints are deprecated.

​
Updated Response Structure

PATCH /community_interactions/{message_id} now includes a conversation object in its response and writes actions at the message level.

​
Update Filters

is_archived will continue to work during migration.

​
Workflow Comparison

​
Before (Conversation-Level)

  1. GET /community_interactions
    • Returns conversation summaries
  2. GET /conversations/{platform}/{conversation_id}/messages
    • Fetch full message thread
  3. POST /conversations/{platform}/{conversation_id}/messages
    • Send reply
  4. PATCH /conversations/{platform}/{conversation_id}/messages/{message_id}
    • Update message

​
After (Message-Level)

  1. GET /community_interactions
    • Returns individual messages
    • Use text for content
    • Includes conversation_id
  2. (Optional) GET /conversations/{conversation_id}
    • Fetch full thread if needed
  3. POST /conversations/{conversation_id}/messages
    • Send reply
  4. PATCH /community_interactions/{message_id}
    • Update message

​
Additional Changes

Reporting APIs: The following endpoints now include DM messages in their calculations. If your brand has active DMs, expect higher counts in volume and sentiment metrics.
  • POST /sentiment_distribution_stats
  • POST /sentiment_time_series
  • POST /volume_time_series
  • POST /top_keywords
  • GET /overview_stats
If you are unsure whether your integration is impacted, please contact our team for assistance.