Replies to a public X (Twitter) post as structured records with author, text and engagement, cursor-paged about 20 per page.
2 credits/ call
Never more than 4 credits a call.
You only pay when data comes back.
curl -X POST "https://api.primaryapi.com/v1/run/twitter.replies" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://x.com/NASA/status/1846987139428634858"}'{
"output": {
"found": true,
"data": {
"nextCursor": "<string | null>",
"items": [
{
"likeCount": "<integer | null>",
"replyCount": "<integer | null>",
"quoteCount": "<integer | null>",
"repostCount": "<integer | null>", …
}
]
}
},
"credits": 2
}Input and output
3 fields
https://x.com/NASA/status/1846987139428….16 fields
cursor for the next page; null at the endGood to know
A page holds about 20 results.
An empty page is found: false. Does not assert whether the post exists. A miss is an answer, not an error.
One page per call. Send nextCursor back as cursor to read the next page.
The same key and credits work for every API.