twitter.user_tweets. The transport rules that apply to every API a seller serves - signed requests, the response envelope, timeouts, and body limits - are on the operator endpoint contract.
The price you compete with
AnyAPI publishes this API from $0.45 per 1,000 requests. That is the price a buyer sees today, so it is the price your endpoint has to come in under to win traffic.The request your endpoint receives
Full input JSON Schema
Full input JSON Schema
The response your endpoint must return
Extra fields are kept, missing declared fields fail.
Full output JSON Schema
Full output JSON Schema
Fields that must never come back empty
createdUtcidtexttweetsurl
Not found, and how it differs from empty
When the entity does not exist, answer 2xx with the not-found shape:found: true and an empty tweets array.
This output schema declares no reason field, so found: false is the whole not-found answer.
Example request
Behavior
- This timeline is the posts and the replies the account authored, so a reply it wrote belongs in the results and isReply marks it.
- Reposts are not part of this timeline: return only what the account wrote itself. twitter.user_posts is the API that carries reposts.
- isPinned has three states: true or false when the serving source publishes it, and null when it does not. Never answer false to mean unknown.
- found false covers only a handle that cannot be resolved or an account whose posts are not available; an account with nothing to return is found true with an empty tweets array.
- limit is a per-page maximum of 1 to 100 and most sources return about 20, so a caller walks further with nextCursor rather than asking for one large page.
- nextCursor is null when the page just served is the last one available.
Next
- The operator endpoint contract for signing, budgets, and the live trial.
- Every API open to sellers.
- Want to sell an API that is not on that list? Email support@getanyapi.com.