X API guide

Quickstart

Start with X

Read public accounts, their posts and replies to a known post. Preserve conversation IDs and reply relationships when analysing a discussion.

These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.

1. Read the account

Use the username without @. Verification and public counts describe the returned account snapshot. Parameters and current cost →

x/profile

curl "https://www.monocrawl.com/v1/x/profile?handle=nasa" \
  -H "x-api-key: mn_your_key_here"

2. Collect a page of posts

Keep each post ID as a string and retain its original URL. Follow only the continuation returned by this endpoint. Parameters and current cost →

x/tweets

curl "https://www.monocrawl.com/v1/x/tweets?handle=nasa" \
  -H "x-api-key: mn_your_key_here"

3. Open one post

Replace the example URL with a returned post URL. The result contains the text, author and available engagement counts. Parameters and current cost →

x/tweet

curl "https://www.monocrawl.com/v1/x/tweet?url=https%3A%2F%2Fx.com%2Fnasa%2Fstatus%2F2095621168208248911" \
  -H "x-api-key: mn_your_key_here"

Filters and coverage

Choose filters with the source behavior in mind

Control	Behavior and limits
Keyword discovery	mode defaults to latest (newest first); top uses source relevance ranking. mode wins over sort, which wins over sort_by. Query operators include from:handle, to:handle, lang:en, min_faves:100, quoted phrases and -word. from_date/to_date set ISO-date bounds. Set include_reposts explicitly to true or false: omitted behavior can vary across sources. Keep the same query, mode and repost setting across pages. Endpoint reference →
Identity	Use the account handle without @. Retain post IDs as strings and pass the source post URL to tweet. Names and biographies are account-entered text, not verified identity. Endpoint reference →
Account feeds	Carry the handle and opaque cursor together. Account feeds, replies and media are different views; do not reuse their tokens across endpoints. Returned ordering can include pinned or source-ranked content. Endpoint reference →
Reply scope	Supply the post ID; the route also accepts a post URL. from_date and to_date are ISO-date filters for this reply operation. Do not assume an account feed supports those same filters. Endpoint reference →
Relationships and coverage	Keep in_reply_to_id and conversation_id where supplied. Reply and quote counts do not include the text of those posts. Protected, deleted or unavailable posts may not be retrievable. Endpoint reference →
Metric meaning	Retweets, replies, quotes, bookmarks and views are separate source counters. Missing views are unknown. verified_blue denotes the source’s blue-verification flag, not an independent identity check. Endpoint reference →

Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.

Choose an endpoint

Match the operation to your task

Your task	Endpoint	When to use it
Replies to one post	`tweet-replies`	Use the numeric post ID and preserve conversation and parent IDs.
Posts matching a phrase	`search-tweets`	Choose latest or top and use advanced query operators for account, language or exact-phrase constraints.
Media from an account	`user-media`	A media-specific account view with its own continuation contract.
Quoted posts	`quotes`	Quotes and replies are different relationships; inspect the endpoint’s accepted identifier.
A profile and recent posts together	`profile/full`	A bounded bundle, with component success and sample statistics.

Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.

Other operations

Posts and media

Accounts and audiences

Search and discovery

Comments and replies

tweet-replies

Transcripts

tweet-transcript

Operations

X

Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.

live · proven: a real upstream response has been served through this API and recorded
wired · unproven: a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
sample · free: no live upstream — /v1 refuses it, /sandbox returns a marked sample

X

16 operations

Elsewhere

The same registry, other shapes

X overview — supported data categories and use cases for this platform.
Full endpoint reference — every platform on one page.
/openapi.json or /openapi.yaml — the machine-readable contract, for Postman, Insomnia or a client generator.
GET /v1/utility/endpoints?platform=x — the same rows to your code at runtime, for 0 credits.