Posts-tab timeline of a public X account: pinned post first, then newest posts, about 20 per page with cursor paging.
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.user_posts" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"handle":"nasa"}'{
"output": {
"found": true,
"data": {
"nextCursor": "<string | null>",
"tweets": [
{
"likes": "<integer | null>",
"retweets": "<integer | null>",
"replies": "<integer | null>",
"isPinned": "<boolean | null>", …
}
]
}
},
"credits": 2
}Input and output
2 fields
nasa.21 fields
cursor for the next page; null at the endGood to know
Public, logged-out data only. Still personal data, so callers carry lawful-use responsibility.
One page per call. Send nextCursor back as cursor to read the next page.
Unknown handle? It comes back as not found, not as an error.
The same key and credits work for every API.