Solutions · Customer support

Customer support over X direct messages

Bring your X inbox into your helpdesk: read conversations, answer customers by DM, and pick up public questions from mentions. Each action is one call, the same price as a read: $0.065 to $0.10 per 1,000.

Get an API key Direct message endpoints →

Works with encrypted X Chat: send the account's X Chat passcode with the request. X session guide

POST /client/dm/conversation format=simple

{

"cookie": "auth_token=…; ct0=…",

"proxy": "http://user:pass@host:port",

"passcode": "<X Chat passcode>",

"user_id": "<customer_id>" }

← 200 "My order hasn't arrived, can you check?"

reply

POST /client/dm/send

{ cookie, proxy, passcode,

"user_id": "<customer_id>",

"text": "Sorry about that! Could you send the order number?" }

← 200 sent, end-to-end encrypted

Direct messages

Read and answer the inbox

Each line is one endpoint and one call.

List conversations, with the latest messages
/client/dm/inbox
Without the passcode: participants and settings only
Read one conversation
/client/dm/conversation
Newest first, with a cursor for older messages
Reply to the customer
/client/dm/send
Text up to 10,000 characters
Check who can message you
/client/dm/settings
Read receipts and call settings too; change them with the update call

Public questions

Catch questions asked in public

Many customers ask in a reply or a mention instead of a DM. Pick those up too and answer where they asked.

01
Find the mentions
Search for your handle with /search on a schedule, or watch accounts with account monitoring and get new tweets by webhook.
02
Route them to your team
Create a ticket per mention in your helpdesk, the same way as for DMs.
03
Answer in public or move to DMs
Reply with /client/reply, or ask the customer to send you a DM when you need an order number or other private details.

How it works

What each request carries

Every call is a POST with the support account's session cookie (auth_token, ct0 and twid), a proxy and, to read or send messages, the X Chat passcode.

Messages are decrypted and encrypted on our server while your request runs; the API does not store messages or the passcode.
The same wrong passcode is never sent to X twice, and the API stops trying when only a few attempts are left.
With format=simple messages come back as flat objects with sender, time, text and attachments.

Direct message endpoints

Use your own account or one you're authorised to manage, and follow X's rules on automation.

FAQ

Support over DMs questions

Why do I need the X Chat passcode?

Direct messages on X are end-to-end encrypted (X Chat). The passcode unlocks the account's chat keys so messages can be decrypted and encrypted while your request runs. It is not stored. Listing conversations and reading settings work without it.

Can I send images in a DM?

No, sending is text only for now. Incoming attachments are listed in the message.

Can I message people who never wrote to us?

This page is about answering customers. The first message to someone starts an encrypted conversation and needs X Chat on their account, and X's rules apply: no unsolicited bulk messages.

How do I catch new messages?

Poll the inbox on a schedule that fits your response time, and keep the newest message ID per conversation so each message is handled once.

Which account does this act on?

The one whose X session (cookie) you send: your brand's support account, or a client's account you manage with their consent.

Get a key, copy your support account's X session, and read the inbox. New accounts start with $0.50 free credit.