If you are building alerts, research tools, or dashboards, you usually want the same thing: a Twitter search API (or X search API) that returns normalized posts you can trust in code—not a brittle HTML parse that changes when the site does.

Social Fetch now exposes GET /v1/twitter/search: search Twitter posts by keyword, with optional filters and stable pagination.

What you can do

• Keyword search — pass a query string to search public posts on X the way a user would in the search box.
• Tune the feed — optional section (top, latest, people, photos, videos), plus minimums for likes, retweets, and replies when you need higher-signal results.
• Time and language — optional startDate and endDate in YYYY-MM-DD form, and a language filter when you want to narrow the corpus.
• Pagination — responses include data.page.nextCursor and data.page.hasMore. Pass the next cursor as cursor on the following request. Pagination uses an opaque cursor returned by a previous response, so your client does not manage vendor-specific tokens by hand.

Successful responses use the same envelope as the rest of the API: data plus meta with requestId, creditsCharged, and version—handy when you are logging support tickets or reconciling usage.

Pricing

This endpoint is metered at 2 credits per completed request (see meta.creditsCharged on the response). For bundles and volume, start at Pricing.

Where to go next

• Reference — full parameters and response shape: Search Twitter posts
• First request — auth, headers, and the success envelope: Quickstart

If you have been searching for a Twitter keyword search API you can call from a backend job or a product, this is the straight line from search intent to documented JSON.