cryptonomads.org APIcryptonomads.org ↗
Access crypto events, job listings, coliving stays, company profiles, and member data from CryptoNomads.org via a structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/25856da9-2315-4e66-a20b-a80bcb00422a/list_main_events?location=Europe' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns a list of main crypto events. Supports filtering by chain, event type, location, and keyword query. Returns all events when no filters are provided.
| Param | Type | Description |
|---|---|---|
| chain | string | Filter by blockchain chain (e.g. 'Ethereum', 'Solana', 'Multichain'). Matches against event chain tags. |
| query | string | Search keyword matched against event name and description. |
| location | string | Filter by location. Matches against city, country, or region fields (e.g. 'Europe', 'Prague', 'USA'). |
| event_type | string | Filter by event type (e.g. 'Conference', 'Hackathon', 'Coliving'). |
{
"type": "object",
"fields": {
"data": "array of event objects with id, event, slug, city, country, region, tags, startDate, endDate, description, link",
"status": "string, always 'success'"
},
"sample": {
"data": [
{
"id": "recEHz3wdRzKFz66Z",
"city": [
"Kaş"
],
"slug": "ZuKaş-2026",
"tags": [
"Ethereum/EVM",
"Coliving"
],
"event": "ZuKaş",
"region": [
"Europe"
],
"country": [
"Turkey 🇹🇷"
],
"endDate": "2026-05-10",
"startDate": "2026-04-10"
}
],
"status": "success"
}
}About the cryptonomads.org API
The CryptoNomads.org API covers 13 endpoints spanning crypto events, job listings, coliving stays, company profiles, and community members. Use list_main_events to browse and filter upcoming conferences, hackathons, and colivings by chain, location, or event type, or call list_jobs to pull open positions filterable by arrangement, job type, and location — all returned as structured JSON with consistent status and data envelopes.
Events and Side Events
list_main_events returns event objects with fields including id, slug, event, city, country, region, tags, startDate, endDate, description, and link. You can filter by chain (e.g. 'Ethereum', 'Solana', 'Multichain'), event_type (e.g. 'Conference', 'Hackathon', 'Coliving'), location, or a keyword query. Pass a slug from those results to get_main_event_detail to retrieve additional fields: organizer, topics, and the full description. get_popular_events returns the top 10 events ranked by user attendance count — useful for surfacing high-interest listings without building your own ranking.
Side events have their own two-endpoint flow. list_side_event_groups returns group-level metadata: title, slug, location, date, endDate, numEvents, and image. get_side_event_group_detail expands a group by its slug into three parts: group metadata, a sideEvents array of individual events, and a companiesAttending array. list_event_companies_attending gives direct access to the company list for a side event group, including each company's name, logo, description, website, tags, and associated users.
Jobs and Companies
list_jobs returns job objects with position, display_name, city, country, job_type, work_arrangement, application_url, and description. Optional filters include query (matches position title or company name), job_type, location, and arrangement. Retrieve full details for a specific posting via get_job_detail using the numeric id. list_companies_hiring returns companies sorted by job_count descending, with company_id, display_name, avatar_url, about, and twitter_handle — useful for identifying active hiring orgs without iterating job listings manually.
Members and Coliving
list_members returns an array of string record IDs for all public members. To get profile data, pass a Twitter handle or Ethereum wallet address to get_member_profile, which returns display_name, twitter_handle, avatar_url, bio, about, website, and company_users. At least one of the two lookup params is required. get_coliving_listings returns events tagged as 'Coliving' using the same schema as main events: id, event, slug, city, country, tags, startDate, endDate, and description — no separate filter step needed.
- Build a crypto event calendar filtered by chain (e.g. Solana, Ethereum) and region using
list_main_events. - Display open crypto jobs filtered by remote arrangement and job type via
list_jobs. - Show companies currently hiring in the crypto space with open position counts from
list_companies_hiring. - Look up a community member's profile by Twitter handle or Ethereum wallet address with
get_member_profile. - Surface the most attended upcoming events using
get_popular_eventsfor a trending events widget. - List coliving retreats and nomad-friendly events by date and location using
get_coliving_listings. - Enumerate companies attending a specific side event group to build a sponsor or attendee directory via
get_side_event_group_detail.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does CryptoNomads.org have an official developer API?+
How does `get_member_profile` identify a member — can I look them up by name?+
handle (case-insensitive) or an Ethereum wallet address; at least one must be provided. Name-based lookup is not currently supported. list_members returns all public record IDs, but retrieving profiles requires a handle or wallet. You can fork this API on Parse and revise it to add name-based search if that data is available.Do the event endpoints return pagination tokens for large result sets?+
list_main_events and list_jobs, use the available filter params (chain, location, event_type, arrangement) to narrow result sets. If paginated access becomes necessary, you can fork the API on Parse and revise it to add limit/offset parameters.Does the API expose event ticket prices or registration fees?+
link and application_url (for jobs) pointing to external registration pages. You can fork this API on Parse and revise it to extract pricing data if it appears on individual event pages.What does `list_side_event_groups` return versus `get_side_event_group_detail`?+
list_side_event_groups returns lightweight group metadata: id, title, slug, location, date, endDate, numEvents, and image. It is intended as a discovery layer. get_side_event_group_detail takes a slug from those results and returns the full group object, the individual sideEvents array, and the companiesAttending array — making it the right call when you need the actual event list or company roster for a specific group.