Social Fetch
Start for freeStart free
Polymarket hub

Polymarket Event Insights API

The written context behind an event, as text, with the update time.

GET /v1/polymarket/events/{eventIdOrSlug}/insights

1 credit Failed requests are free

Try in playgroundFull API docs

About this endpoint

GET /v1/polymarket/events/{eventIdOrSlug}/insights returns data.insights for one event: text, a summary of the news and context behind the event's prices, and updatedAt, when that text was written. data.eventId repeats the event id and data.lookupStatus tells you whether the event exists.

The text is machine written and the dates inside it can be old, so treat it as context rather than a live feed. An event with no written insights returns insights: null on a found lookup.

Polymarket Event Insights API FAQ

Why is insights null on a found event?

Not every event has written context. A found lookup with insights: null means the event exists and has no insights text right now. Check the key, then fall back to the event description or the annotations route.

Is the text live or historical?

It is a written summary attached to the event, not a live price feed. updatedAt tells you when it was written, and dates mentioned inside the text can be older than that. Read prices from the market, books or prices routes.

Where do the sources for a price move live?

Insights are prose without citations. Use GET /v1/polymarket/events/{eventIdOrSlug}/annotations for dated explanations that carry a sources array with publisher names and links.

What does lookupStatus mean on this route?

found means the object or list was returned. not_found means no matching object exists. HTTP 200 only means the request finished, so branch on data.lookupStatus before storing a row.

How much does this route cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.

Other Polymarket endpoints