Search for Twitter geographic places by name, coordinates, or IP address and retrieve complete place metadata, country information, place types, and geographic bounding boxes as structured JSON.
{
"data": [
{ "id": "place_001", "name": "New York", "woeid": 2459115, "country": "United States", "type": "City" },
{ "id": "place_002", "name": "New York, NY", "woeid": 2459115, "country": "United States", "type": "Admin" }
]
}Pick an endpoint to see what it does, which parameters it accepts, and the JSON your application receives. Authenticate with your API key in the x-api-key header.
/v1/twitter/geo/searchFind Twitter place entities by name, coordinates, or IP address. Get WOEIDs for trend lookups and place IDs for geo-tagged tweet analysis.
query | optional | Place name to search for (e.g., "New York") |
lat | optional | Latitude coordinate |
long | optional | Longitude coordinate |
{
"data": [
{ "id": "place_001", "name": "New York", "woeid": 2459115, "country": "United States", "type": "City" },
{ "id": "place_002", "name": "New York, NY", "woeid": 2459115, "country": "United States", "type": "Admin" }
]
}Convert free-form location names, coordinates, or IP-based location signals into structured Twitter place entities. Store normalized place IDs, names, countries, country codes, and place types in your application.
Enrich location-based social datasets with standardized geographic metadata. Resolve place IDs found in Twitter data and attach normalized names, regional context, country information, and geographic boundaries.
Use bounding-box coordinates to display Twitter place entities on maps, create regional overlays, or organize location-based data by country, administrative region, city, neighborhood, or point of interest.
Validate user-entered locations and normalize inconsistent place names into stable Twitter place objects. Distinguish between cities, countries, administrative regions, neighborhoods, and points of interest before storing or analyzing geographic data.
Sub-100ms response times. Most of that is your network latency, not our infrastructure. Deploy, test, iterate the same day instead of week-long proofs-of-concept.
99.9% uptime SLA. Your data pipeline doesn't stop because X changed a selector. Monitoring, patching, and infrastructure are all us. You focus on what you built.
Tweets, profiles, followers, communities, trends, geo, real-time Streams — 40+ endpoints. Whatever you need from X, it's here. No fragmented tooling, no API gaps forcing you to bolt on a second service.
RESTful API, SDK support (Python, Node, Go, PHP), MCP, CLI, and no code. Use it in an existing system or a new greenfield; the response shape never surprises you.
Use ScrapeBadger through an official SDK, a standard API request, a real-time connection, or the tools already in your workflow.
Build asynchronous data pipelines with typed responses, automatic pagination, retry handling, and access to the complete Twitter API.
Add Twitter data to Node.js and TypeScript applications with type definitions, async pagination, and support for both ESM and CommonJS.
Connect from any backend or programming language using standard HTTP requests. Responses arrive as structured JSON that can be stored, transformed, or passed into another service.
Receive new tweets through a persistent WebSocket connection or deliver them directly to your application through signed webhooks. Available with Twitter Streams for account and query monitoring.
Give compatible AI agents access to Twitter profiles, tweets, search, trends, communities, lists, and monitoring tools through ScrapeBadger's MCP server.
Search tweets, retrieve profiles, inspect trends, and export results as JSON, CSV, Markdown, or terminal-friendly tables without writing an application.
See what our customers say about ScrapeBadger Twitter API.
“We switched from the official Twitter API and cut our costs by 95%. The pagination is seamless, and we've never hit a rate limit. Best decision we made this year.”
“The follower and engagement endpoints are incredibly detailed. We use it for influencer research and competitor analysis. Response times are sub-100ms consistently.”
“Started with the Apify actor, then moved to the API for more control. The 1,000 free credits were enough to build our MVP. Now processing 2M+ tweets monthly.”
“Perfect for academic research. The community and trends endpoints give us data we couldn't get anywhere else. Documentation could use more examples, but support is responsive.”
“We monitor 50,000+ accounts for our clients. ScrapeBadger handles it without breaking a sweat. The bulk ID endpoints are a game-changer for large-scale monitoring.”
“The geo and trends endpoints power our location-based analytics. Setup took 10 minutes. Their Apify actors are also great for quick one-off scrapes.”
Start with pay-as-you-go credits (never expire) or save up to 64% with a monthly or annual subscription. Failed requests never consume credits, and the exact charge is returned in the X-Credits-Used response header.
Every endpoint uses the same model: 1 base credit + 1 credit per item returned. Single-item lookups always cost 2 credits. Paginated list endpoints cost 1 + the number of items in the page. Failed requests cost 0 credits.
Everything you need to know about the Twitter Geo API.
Sign up free and get 1,000 API credits. No credit card required.
Disclaimer: ScrapeBadger is not affiliated with, endorsed by, or in any way officially connected with X Corp. (formerly Twitter, Inc.) or any of its subsidiaries or affiliates. The names Twitter, X, and related trademarks are the property of their respective owners.