CoronaCrush APIcoronacrush.co ↗
Access upcoming Jewish speed dating events from CoronaCrush via API. Get event dates, timezones, prices, signup counts, and registration links in one call.
What is the CoronaCrush API?
The CoronaCrush API exposes 1 endpoint that returns all upcoming Jewish speed dating events published on coronacrush.co. The list_events endpoint delivers a full array of event objects, each containing 6 fields: event_id, date, timezone, price, current signup count, and a direct signup URL. No parameters are required — a single request returns the complete current event schedule.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/98bbe11e-d7c0-4f53-b293-185ad85e4041/list_events' \ -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 coronacrush-co-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.
"""Walkthrough: CoronaCrush SDK — list upcoming Jewish speed dating events."""
from parse_apis.coronacrush_co_api import CoronaCrush, ParseError
client = CoronaCrush()
# List all upcoming events, capped at 3
for event in client.events.list(limit=3):
print(event.date, event.timezone, event.price, event.signups)
# Grab the first event for inspection
try:
first = client.events.list(limit=1).first()
if first:
print(first.event_id, first.signup_url)
except ParseError as e:
print(f"error: {e}")
print("exercised: events.list")
Returns all upcoming Jewish speed dating events with date, timezone, price, signup count, and registration link. Results come as a single page; the site publishes only current upcoming events.
No input parameters required.
{
"type": "object",
"fields": {
"events": "array of upcoming event objects with event_id, date, timezone, price, signups, and signup_url"
},
"sample": {
"events": [
{
"date": "Jul 29 at 9:00PM",
"price": "FREE",
"signups": "1,486 singles already signed up!",
"event_id": "TfO4Muj09TPLUdet",
"timezone": "Israel Time",
"signup_url": "https://coronacrush.co/coronacrush?eid=TfO4Muj09TPLUdet"
},
{
"date": "Jul 29 at 9:00PM",
"price": "FREE",
"signups": "2,965 singles already signed up!",
"event_id": "BcI2P0MNE77Z0r60",
"timezone": "Eastern Time",
"signup_url": "https://coronacrush.co/coronacrush?eid=BcI2P0MNE77Z0r60"
}
]
}
}About the CoronaCrush API
What the API Returns
The list_events endpoint returns every upcoming event currently listed on CoronaCrush. Each event object in the response array includes a unique event_id, an event date, the timezone the event is scheduled in, the price to attend, the current signups count, and a signup_url pointing directly to the registration page for that event.
Endpoint Behavior
list_events takes no input parameters. The response is a single, unpaginated array covering all events CoronaCrush has currently published. Because the source only surfaces upcoming events, past or archived events are not included in the response. The dataset reflects whatever CoronaCrush has listed at the time of the request.
Coverage and Scope
All events returned are Jewish speed dating events organized through CoronaCrush. The data includes both pricing and live signup counts, making it straightforward to track event capacity trends or surface events with available spots. The signup_url field links directly to each event's registration page, so downstream applications can route users to sign up without any additional lookup.
The CoronaCrush API is a managed, monitored endpoint for coronacrush.co — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when coronacrush.co 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 coronacrush.co 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?+
- Display a live calendar of upcoming CoronaCrush events with dates and timezones on a community site
- Monitor signup counts across events to detect which events are filling up fastest
- Build a price comparison view across all upcoming events using the price field
- Send automated alerts when new events appear in the list_events response
- Aggregate CoronaCrush events into a broader Jewish singles events aggregator alongside other sources
- Track event frequency and scheduling patterns over time by logging list_events responses
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.