Search tech events by name, date and location

View all Crunchbase Company & Investment Data endpoints →

Search Crunchbase technology conferences and other events with optional name, industry, location, event-type and start-date filters. query matches text in the event name. category accepts an industry permalink, UUID or name; location accepts a location permalink, UUID or name. event_type supports conference, meetup, hackathon, demo_day, networking, competition, seminar, webinar, expo, class, festival and other. starts_after and starts_before use YYYY-MM-DD and include their boundary dates. sort accepts starts or rank and defaults to starts; the documentation does not specify sort direction. page accepts integers from 1 through 100 and defaults to 1. No parameter is required. The unverified documentation response example contains count, current_page, per_page, total_pages, next, previous, sort and items. Each event item includes id, uuid, name, link, image, short_description, rank, starts_on, ends_on, categories, category_groups and location. Category and category-group entries contain id and name. The location object contains city, region, country, continent, groups and ids. previous is null in the example's first page. No response was observed for this endpoint in the supplied evidence, so these documented example fields are not a verified schema or a guarantee that every field will be populated. Use returned event identifiers to continue with event-detail or participant research. Check starts_on and ends_on before labeling an event as upcoming; a name match alone does not establish that it is in the future.

API Features

Name and sector discovery Find event names containing your query text and narrow the candidate set with an industry supplied as a name, permalink or UUID.
Inclusive start-date windows Combine starts_after and starts_before in YYYY-MM-DD format to include events starting on either boundary date.
Twelve documented event formats Filter by formats such as conference, meetup, hackathon, demo_day, webinar or expo using the event_type parameter.
Location-aware calendar candidates Filter a geographic area by name, permalink or UUID; the documentation example includes event start and end dates plus structured location fields.
Start-date or rank ordering Choose starts or rank for the sort parameter and request result pages 1 through 100. Ordering direction is not specified in the supplied documentation.

Live API Demo

GET /api/project/crunchbase/search-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/search-events?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Do I need to provide a search query?

No. All eight parameters are optional. When provided, query matches text contained in the event name, such as summit; it is not documented as a general full-text search across descriptions.

Are starts_after and starts_before inclusive?

Yes. starts_after means the event starts on or after the specified date, while starts_before means it starts on or before it. Use YYYY-MM-DD for both parameters.

How should I identify an industry or location?

category accepts an industry permalink, UUID or name. location likewise accepts a location permalink, UUID or name. These filters are distinct from query, which searches the event name.

Which event types can I filter?

The documented event_type values are conference, meetup, hackathon, demo_day, networking, competition, seminar, webinar, expo, class, festival and other.

How are sorting and pagination controlled?

sort accepts starts or rank, with starts as the documented default. Sort direction is not specified. page defaults to 1 and supports 1 through 100. Pagination fields in the documentation example include current_page, per_page, total_pages, next and previous.

Are the example dates and response fields verified live results?

No response was observed for this endpoint in the supplied evidence. The described item and pagination fields come from a documentation example. Validate the actual returned dates before calling an event upcoming, and do not assume every example field is always populated.

Related operations

Guides

View Subscription Plans →