CryptoNomads APIcryptonomads.org ↗
Access crypto events, job listings, coliving stays, company profiles, and member data from CryptoNomads.org via a structured JSON API.
What is the CryptoNomads 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.
curl -X GET 'https://api.parse.bot/scraper/25856da9-2315-4e66-a20b-a80bcb00422a/list_main_events?chain=Ethereum&query=summit&location=Europe&event_type=Conference' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace cryptonomads-org-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""CryptoNomads SDK — discover crypto events, jobs, and community members."""
from parse_apis.cryptonomads_api import CryptoNomads, ResourceNotFound
client = CryptoNomads()
# List popular crypto events — capped at 5 items total.
for event in client.events.popular(limit=5):
print(event.name, event.start_date, event.city)
# Search events by keyword, take the first result and inspect it.
event = client.events.search(query="ethereum", limit=1).first()
if event:
print(event.name, event.slug, event.tags)
# List side event groups then drill into one group's attending companies.
group = client.sideeventgroups.list(limit=1).first()
if group:
for company in group.companies.list(limit=3):
print(company.name, company.logo, company.tags)
# Browse remote crypto jobs.
for job in client.jobs.list(arrangement="Remote", limit=3):
print(job.position, job.display_name, job.work_arrangement)
# Typed error: attempt to fetch a non-existent event.
try:
detail = client.events.get(slug="nonexistent-event-9999")
print(detail.name)
except ResourceNotFound as exc:
print(f"Event not found: {exc}")
print("exercised: events.popular / events.search / sideeventgroups.list / group.companies.list / jobs.list / events.get")
Returns all main crypto events. Supports client-side filtering by chain, event type, location, and keyword query. Returns all events when no filters are provided. Results are not paginated — the full event calendar is returned in one response.
| 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": {
"items": "array of event objects with id, event, slug, city, country, region, tags, startDate, endDate, description, link"
}
}About the CryptoNomads API
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.
The CryptoNomads API is a managed, monitored endpoint for cryptonomads.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when cryptonomads.org changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official cryptonomads.org API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- 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 | 100 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.