Dev.to Events API
Challenges, live streams and takeovers on Dev.to, with their times and stream links.
GET /v1/dev-to/events1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/events returns every event in one response as events, with total set to the number of rows. Each event has id, title, description, type, slug, variationSlug, startsAt, endsAt, broadcastEndedAt, streamUrl, chatUrl, details, coverImage, backgroundColor, tags, createdAt and updatedAt.
Send type to keep one kind: challenge, live_stream, takeover or other. Omit it for all events. This route has no page parameters because Dev.to returns the whole list at once. Dates are ISO-8601 and can be null when an event has no start or end time, and broadcastEndedAt is null until a live broadcast ends.
Dev.to Events API FAQ
Why is there no paging?
Dev.to returns the event list in one response, so the route has no page or limit parameters and charges one request. Read total and the length of events.
How many credits does the events list 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.
What are the event types?
challenge, live_stream, takeover and other. Send one as type to filter, or omit type to get every kind.
What do streamUrl and chatUrl point to?
The embedded stream and chat, when the event has them. Either can be null for an event without a live component.