Polymarket APIFetch Polymarket prediction markets as structured JSON with one SocialCrawl API key. One advanced research composite expands your topic, fans out queries, and ranks on-topic events. Reads are priced in credits.
1 active endpoint. Advanced research composite.
One live read endpoint for public Polymarket data. Pass a research topic and get a curated set of prediction markets: event titles, market questions, outcome prices, volume, and end dates. Data API only. No trading or wallet actions.
/v1/polymarket/researchServer-side multi-query fan-out over public Polymarket markets. Expands the topic into parallel searches, dedupes events, drops off-topic matches, and ranks by topic-to-title similarity. Returns event title, market questions, outcome prices, volume, and end date.
query, limit
Returns Polymarket prediction markets about a topic, ranked by how well they match: event title, market questions, outcome prices, volume, and end date.
Use it to get a focused feed of markets on a subject. It runs several searches for you and drops results that are not about the topic.
query · The research topic — free-text natural language (e.g. 'last 30 days bitcoin halving', 'kanye west tour'). Framing prefixes like 'last N days' and 'what are people saying about' are stripped automatically before expansion.
$ curl https://www.socialcrawl.dev/v1/polymarket/research?query=trump+2028+election \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key — hit "Try it" to see an example responsePolymarket is a normal SocialCrawl surface. You call GET /v1/polymarket/research with an API key, spend credits on live misses, and get a single JSON envelope back. No Polymarket wallet. No second SDK.
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog. No Polymarket account or trading credentials.
The live route is GET. Pass query as free-text topic text. Optional limit bounds results per fan-out leg. Framing phrases are stripped before expansion.
Research costs 5 credits per live miss because it hits upstream several times. Cache hits cost 0. Empty or hard failures refund. Bad params never charge.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Market rows sit under data with the shared SocialCrawl envelope fields.
Most products research a topic once, keep the ranked markets, then re-run when the narrative shifts. There is no multi-endpoint drill-down chain on Polymarket today.
GET /v1/polymarket/research?query=…&limit=10A free-text research query (entity, election, event, or market theme)
One string drives the whole fan-out. Framing prefixes are stripped automatically.
# expand topic into multi-query fan-outRanked events with markets, outcome prices, volume, and end dates
Server expands queries, filters off-topic hits, and ranks on-topic markets.
# dedupe, filter, rank marketsThe subset of markets you care about for alerts or dashboards
Downstream products usually watch a short list, not every returned event.
# return ranked research payloadA newer ranked set when prices or volume matter again
Cache hits keep repeats cheap. Live misses re-run the multi-query composite.
GET /v1/polymarket/research
?query=us+election+odds
&limit=10
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here{
"success": true,
"data": {
"query": "us election odds",
"markets": [
{
"id": "market_…",
"title": "Example market",
"url": "https://polymarket.com/…",
"ext": {
"volume": 1200000,
"probability": 0.62
}
}
]
},
"credits_used": 5,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Polymarket is an Analytics-style search surface. Field names stay under the shared SocialCrawl envelope so your client code does not grow a second response parser.
success, data, credits_used, credits_remaining, request_id, cached
ranked events: title, slug, markets[], volume, liquidity, end date, price changes when present
market questions, outcome prices, related event linkage, volume signals
topic-derived fan-out ranking after dedupe and off-topic filter (server-side composite)
Same request lifecycle as every other /v1 platform endpoint. Polymarket is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency per key.
Registry lookup finds polymarket/research. Required query checks run first. Invalid input returns 400 with no charge. Valid calls debit 5 credits before upstream work.
A deterministic cache key is built from platform, resource, and params. Hit: return immediately, credits_used = 0. Miss: expand the topic into up to six searches, call the public Gamma API in parallel, dedupe and filter, then rank.
Upstream market JSON is shaped into the SearchResult payload, wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
Polymarket research reads public prediction market data and returns a ranked topic feed. Your code does not talk to Gamma or run multi-query fan-out itself.
Public prediction markets and events. Read-only research surface for topic monitoring, narrative tracking, and product jobs. No order placement or wallet access.
A dedicated Polymarket fetcher calls the public Gamma API. Research expands one topic into parallel searches, dedupes by event id, filters unrelated matches, and ranks the rest.
A unified JSON envelope: success, data, credits_used, request_id, cached. Event and market rows carry titles, questions, prices, volume, and end dates.
No write endpoints. No trading. polymarket/search stays registered but soft-disabled after upstream instability; use research for live topic work.
The jobs this API is most often used for.
Topic-level prediction market research
Callers concentrate on research with a free-text topic when they need on-topic markets without running several searches by hand. One advanced composite expands queries, filters noise, and ranks markets at a flat 5 credits. Same SocialCrawl key and envelope as social platforms.
Research fans out several upstream searches, so live misses take longer than a single-query social read. Cache hits return immediately.
Common ways teams put this data to work, and the stack each one tends to run.
Poll research for elections, crypto, or news topics. Alert when volume or prices on ranked markets move.
Pull a curated market set for a thesis, then join prices and titles into tables without hand-writing multi-query logic.
Wire topic research into dashboards and agent tools. Same API key as the rest of SocialCrawl. Cache hits keep recurring runs cheap.
Research is 5 credits per live call. Cache hits are free. Pass query as the research topic.
curl "https://www.socialcrawl.dev/v1/polymarket/research?query=us+election&limit=10" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Polymarket data, two very different paths. Auth, rate limits, schema, and cost — side by side.
| Feature | SocialCrawl | Polymarket Gamma API |
|---|---|---|
| Authentication | One x-api-key shared with 47 other platforms | No key needed for public Gamma endpoints |
| Setup | One GET to /v1/polymarket/research with a topic | Free, but you write your own search fan-out and aggregation |
| Response schema | Unified data.items envelope, same parser as your social sources | Gamma-specific market objects; CLOB is a separate API for trading |
| Pricing | 5 credits per research call; 100 free credits, no card | Free |
| Data coverage | Aggregated multi-market view per topic: odds, prices, volume, end dates | Full raw market data, one query at a time |
Authentication
Setup
Response schema
Pricing
Data coverage
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl