List a company's recorded event participation
View all Crunchbase Company & Investment Data endpoints →Retrieve recorded event participation for the company identified by the required company query parameter. Documented identifier forms are a Crunchbase organization permalink, company UUID or full crunchbase.com/organization/ URL. The optional page parameter defaults to 1 and accepts integers from 1 through 100. Omit role for an unfiltered request, or choose one documented role: sponsor, speaker, exhibitor, contestant or organizer. The supplied source example describes a paginated object with company, count, current_page, items, next, per_page, previous and total_pages. The company object contains id and uuid. Each example item has id, event, participant, role, event_starts_on, event_location and short_description. The event object contains id, uuid, name, type and link; participant contains the participating organization identity, including id, uuid, name, type, link and image. The example includes null event_location and short_description values, so a record may not have venue details or descriptive text. This operation has no supplied live probe. The response structure, participation records and pagination fields are from an unverified source example, not an observed successful response. Treat these as recorded participation relationships rather than a comprehensive event calendar, proof of current attendance or a commitment to attend a future event. No specific update interval or complete historical coverage is established.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/crunchbase/company-events API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/crunchbase/company-events?key=<API_KEY>&company=openai&page=1'
Query Result
Use Cases
- Prepare a partnership-research calendar from events where a target account is recorded as a sponsor or exhibitor, retaining the requested role with the results.
- Compare recorded conference appearances across a short company list to identify shared industry venues for relationship research.
- Assemble a speaker-participation brief using event names, start dates and participant references, without implying a future speaking engagement.
- Research organizations with contestant or organizer records when building a shortlist of competition partners and ecosystem contacts.
- Design an event-participation import that stores page context and preserves missing venue descriptions rather than inventing location data.
Frequently asked questions
Which company identifier does the events lookup accept?
The documented company input accepts a Crunchbase organization permalink, company UUID or full crunchbase.com/organization/ URL. It identifies one organization; this is not a general company-name or event search.
Which event roles can I filter by?
The documented role values are sponsor, speaker, exhibitor, contestant and organizer. Supply one role to request only that participation role, or omit the optional filter for an unfiltered request.
How do I request another page of participation records?
Use the optional integer page parameter, documented as 1 through 100 with a default of 1. The source example contains count, current_page, per_page, total_pages, next and previous fields. No live probe establishes how many pages a particular company will have.
Which fields are documented for an event participation item?
The unverified example includes id, event, participant, role, event_starts_on, event_location and short_description. The event and participant objects contain their own identity references. Event location and short description are null in the example, so venue and descriptive coverage should not be assumed.
Are these records proof of upcoming attendance or live-verified coverage?
No. There is no supplied live probe for this operation. Its described structure comes from a source example, and recorded participation should not be treated as a current attendance guarantee, future commitment or complete event history.