Extract structured event data from any web page via Diffbot's Event API, paid per call over MPP.
What it does
The Diffbot Event endpoint, served through the Locus MPP (Micropayment Protocol) gateway, extracts structured event information from a given URL. You POST a URL pointing to an event page and receive structured data about the event (title, date, location, description, etc.) as returned by Diffbot's extraction engine. Payment is handled per-call via the Tempo method on pathUSD at $0.0042 per request.
This endpoint is one of several Diffbot extraction APIs available through the same MPP gateway, which also offers article, product, discussion, image, video, list, job posting, and auto-detect (analyze) endpoints — all at the same per-call price. The Event endpoint accepts optional parameters including extra fields to return, a custom timeout, and a flag to extract discussion threads alongside the event data.
The endpoint uses the MPP charge intent, meaning each call is a one-shot payment. Settlement occurs in pathUSD on Tempo L2. The OpenAPI spec is well-defined with a clear request schema, though response schemas are not documented in the spec. Diffbot's own documentation at docs.diffbot.com provides further details on the Event API's output fields.
Capabilities
Use cases
- —Extracting structured event details (date, venue, description) from arbitrary event pages
- —Building an aggregated events database from multiple web sources
- —Enriching calendar or ticketing applications with scraped event metadata
- —Monitoring event listings across websites for changes or new postings
Fit
Best for
- —Agents that need structured event data from arbitrary URLs without managing a Diffbot API key
- —Pay-per-call event extraction without subscription commitments
- —Programmatic pipelines that scrape event pages and need clean JSON output
Not for
- —Bulk crawling thousands of event pages (per-call pricing adds up quickly)
- —Extracting non-event content — use the article, product, or analyze endpoints instead
Quick start
curl -X POST https://diffbot.mpp.paywithlocus.com/diffbot/event \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <MPP_TOKEN>" \
-d '{"url": "https://example.com/events/tech-conference-2025"}'Example
Request
{
"url": "https://example.com/events/tech-conference-2025",
"fields": "links,meta",
"timeout": 30000,
"discussion": false
}Endpoint
Quality
The OpenAPI spec provides a clear request schema and pricing info for the Event endpoint, but the probe did not capture a live 402 challenge (HEAD/GET returned 404; the endpoint expects POST). No response schema is documented, and crawl pages returned only generic 404 JSON. Diffbot's own docs would fill gaps but were not crawled.
Warnings
- —Probe returned 404 on HEAD/GET — endpoint likely requires POST method only; liveness not fully confirmed via 402 challenge
- —No response schema documented in the OpenAPI spec; output structure must be inferred from Diffbot's own documentation
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals (amount 4200 = $0.0042); if decimals differ, price would change
Citations
- —The Event endpoint charges 4200 base units in pathUSD per call via Tempo settlementhttps://diffbot.mpp.paywithlocus.com
- —Diffbot API reference is available at docs.diffbot.comhttps://docs.diffbot.com
- —The OpenAPI spec lists article, product, discussion, image, video, analyze, event, list, and job endpoints all at the same pricehttps://diffbot.mpp.paywithlocus.com