# X messaging API

> Markdown version of https://postlake.dev/social-media-messaging-api/x-twitter . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

Messaging on X through the same call you use for every other network, with X's real rules enforced before anything is sent.

Messaging on X
    List conversations, read one, and reply, through the same shapes you use everywhere else.
    curl "https://api.postlake.dev/v1/conversations?limit=50" \
  -H "Authorization: Bearer $POSTLAKE_API_KEY"
    Every list returns problems alongside the items, naming any network that could not be read. Without that an empty inbox is ambiguous: "nobody messaged" and "we could not look" are the same response, and an agent acting on the first when the second is true will conclude something false.

    Opening a conversation
    Post to /v1/conversations with a handle to open a thread, then send into it. Replies read back in the same shape, so a support loop is a poll of one endpoint rather than a per-network integration.

    What X allows
    X exposes direct messages to applications, and its own rules are strict about unsolicited sending. Automating outreach is what gets accounts restricted, so this is built for replying to people who contacted you, not for cold messaging. That is a limit worth respecting rather than routing around.

    Common questions
    
### Can I send DMs through an API on X?

Yes, X is one of the two networks where this is genuinely available. Conversations and messages come back in the same shape as every other read.

    
### Why do so few networks support this?

Because most do not expose it. Meta requires a heavy app review and business accounts, LinkedIn is partner-only at enterprise pricing, and TikTok, YouTube and Pinterest offer nothing to applications. Any product implying a nine-network inbox is describing something that does not exist.

    
### Can I use this for outreach?

No, and you should not want to. Unsolicited automated messaging is what gets accounts restricted on every network that offers messaging at all. This is built for replying to people who contacted you.

    
### Can an agent handle replies?

Yes, with list_conversations, read_conversation and send_message over MCP. Restrict which brands and networks it may act on before you let it run.

## Related

- [Post to X via API](https://postlake.dev/post-to/x-twitter.md)
- [Scheduling on X](https://postlake.dev/social-media-scheduling-api/x-twitter.md)
- [Analytics on X](https://postlake.dev/social-media-analytics-api/x-twitter.md)
- [Comments on X](https://postlake.dev/social-media-comments-api/x-twitter.md)