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

Company-to-event participation lookup Request the participation records associated with one Crunchbase organization identifier rather than searching a general event directory.
Five documented participation roles Narrow the request to sponsor, speaker, exhibitor, contestant or organizer using the optional role filter.
Event and participant identity references The source example separates the event identity from the participating organization, providing identifiers and profile links for each.
Event start and venue attributes The documented items include event_starts_on and event_location, with nullable location and description fields that should remain unknown when absent.
Numbered participation result pages Request page 1 through 100; the unverified example includes item counts, current and total page fields, and next/previous navigation fields.
Explicit event-evidence boundary The available response example is not live-verified and does not establish complete attendance history or future participation commitments.

Live API Demo

GET /api/project/crunchbase/company-events

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/crunchbase/company-events?key=<API_KEY>&company=openai&page=1'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →