Skip to main content
GET
/
x
/
dm
/
{userId}
/
history
Get DM history
curl --request GET \
  --url https://xquik.com/api/v1/x/dm/{userId}/history \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

1 credit per result returned · All plans from $0.00012/credit
Requires a connected X account passed via the account query parameter. DM history is participant-scoped, so pass the connected account that belongs to the conversation.
DM history responses can contain private message text. Store them in a private support, CRM, warehouse, or agent memory system. Do not write full DM bodies to shared logs or public artifacts.
curl -G https://xquik.com/api/v1/x/dm/44196397/history \
  --data-urlencode "account=your_handle" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Page 2
curl -G https://xquik.com/api/v1/x/dm/44196397/history \
  --data-urlencode "account=your_handle" \
  --data-urlencode "cursor=abc123" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The examples normalize each page into private dm_history rows. Store message_id, sender_id, receiver_id, message_text, created_at, optional media_url, conversation_user_id, sender_account, and page_next_cursor. Keep message_text only in private systems; use the IDs, timestamp, media URL, and job status in shared logs.

​
Path parameters

​
userId
string
required
Target X user ID for the DM conversation (numeric string).

​
Query parameters

​
account
string
required
X handle (without the @ prefix) of the connected X account used to read the conversation. DM history is participant-scoped, so the account must belong to the conversation. Connect an account on the dashboard before calling this endpoint.
​
cursor
string
Pagination cursor. Pass the next_cursor value from the previous response to fetch older messages.
​
maxId
string
Legacy pagination cursor. Use cursor for new integrations. When both are present, cursor takes precedence.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
messages
object[]
Array of direct messages.
​
has_next_page
boolean
Whether older messages are available.
​
next_cursor
string
Opaque cursor for the next page. Empty string when no more messages.
{
  "messages": [
    {
      "id": "1893456789012345678",
      "text": "Hey, great tool!",
      "senderId": "44196397",
      "receiverId": "987654321",
      "createdAt": "2026-02-24T10:00:00.000Z"
    }
  ],
  "has_next_page": true,
  "next_cursor": "1893456789012345677"
}

​
History sync handoff

Use this endpoint when a CRM, support desk, warehouse job, or agent needs participant-scoped DM context before sending a reply.

Dedupe imported messages

Store messages[].id as the external DM ID for CRM notes, support tickets, warehouse rows, or agent memory.

Preserve participants

Store messages[].senderId and messages[].receiverId with the connected account so each private conversation stays tied to the correct sender.

Resume older pages

Store next_cursor when has_next_page is true, then pass it as cursor on the next sync job.

Keep media context

Store optional messages[].mediaUrl with messages[].createdAt when a DM includes an image, GIF, or video attachment.
Related: Direct Message Workflow for lookup, participant-scoped history sync, messageId storage, and media handoff; Get User to resolve the recipient userId; Send DM to reply from the connected account; Upload Media when a reply needs one uploaded mediaId.
Last modified on May 19, 2026