rcdb.com APIrcdb.com ↗
Access roller coaster specs, park details, photo galleries, and search across the RCDB database. 6 endpoints covering coaster stats, status, and location data.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/8a18aea2-34a6-477e-827d-dd8792ab477c/get_random_coaster' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns details of a randomly selected roller coaster from the rcdb.com homepage. Each call returns a different coaster with varying fields depending on available data.
No input parameters required.
{
"type": "object",
"fields": {
"id": "string, numeric coaster ID",
"name": "string, coaster name",
"park": "string, name of the park",
"status": "string, operating status",
"park_id": "string, numeric park ID",
"location": "string, comma-separated location"
},
"sample": {
"data": {
"id": "20044",
"name": "Roller Coaster 5",
"park": "Hebron Fireman's Carnival",
"layout": "Oval",
"status": "Operating",
"park_id": "20043",
"location": "Hebron , Maryland , United States",
"manufacturer": "B. A. Schiff & Associates",
"roller coaster": "5"
},
"status": "success"
}
}About the rcdb.com API
The RCDB API provides structured access to roller coaster and amusement park data across 6 endpoints, pulling from the world's largest roller coaster database at rcdb.com. The get_coaster_details endpoint alone returns over a dozen fields including track dimensions, train configuration, operating status, and status date. Whether you need to look up a specific coaster by ID, browse a park's full ride inventory, or pull photo gallery metadata, the API covers the core data rcdb.com publishes.
Coaster and Park Detail Endpoints
The get_coaster_details endpoint accepts a numeric coaster_id and returns a structured object that includes the coaster's name, park, location, status, status_date, general_info array, and a stats object segmented into sections like Tracks, Trains, and Details. These stat sections contain key-value pairs for measurements such as height, speed, length, inversions, and design type — the same figures listed in the statistics table on rcdb.com. The get_park_details endpoint takes a park_id and returns the park's name, location, and a coasters object where each key is an operating status (e.g. "Operating", "Removed") and each value is an array of coaster objects with name and id.
Search Endpoints
Two search endpoints handle different lookup patterns. search_coasters accepts an optional query string and returns a flat list of all matching coasters with fields name, id, park, park_id, and opened. Omitting the query returns the full coaster list with a total count. quick_search is designed for autocomplete scenarios: it takes a required query and returns a small result set where each item has a title (t), subtitle or location (s), and a relative link path (l). A sequence integer is also returned, which is useful for ordering out-of-sequence async responses.
Photo Gallery and Random Coaster
get_coaster_pictures returns the full photo gallery for a coaster by coaster_id. The response includes a pictures array where each item carries an id, url, name, per-picture dimensions, and multiple size variants. Sprite sheet metadata (sprite_url, cols, width, sizes) is also returned for efficient thumbnail rendering. The get_random_coaster endpoint takes no inputs and returns a randomly selected coaster's basic details — id, name, park, park_id, status, and location — useful for discovery features or sampling the dataset.
- Build a coaster comparison tool using
statsfields like height, speed, and inversions fromget_coaster_details. - Populate a park directory with ride inventory grouped by status using
get_park_detailsand itscoastersobject. - Implement a coaster autocomplete search bar using
quick_searchwith thet,s, andlresponse fields. - Display photo galleries for individual coasters by feeding
pictures[].urland size variants fromget_coaster_pictures. - Generate a 'coaster of the day' feature using
get_random_coasterto surface ride names, parks, and locations. - Export a filtered dataset of coasters with opening years using the
openedfield fromsearch_coasters. - Track historical operating status changes by reading
statusandstatus_datefromget_coaster_details.
| 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 rcdb.com have an official developer API?+
What does `get_coaster_details` return in the `stats` object?+
stats field is a nested object with section keys such as Tracks, Trains, and Details. Each section contains key-value pairs like height, drop, speed, length, duration, capacity, or number of inversions — depending on what rcdb.com lists for that specific coaster. Not every coaster has every stat populated; fields vary based on available data.Does `search_coasters` support filtering by country, coaster type, or manufacturer?+
search_coasters filters only by a keyword query matched against coaster names, and returns name, id, park, park_id, and opened fields. You can fork this API on Parse and revise it to add filter parameters for attributes like location or coaster type.Are user reviews or visitor ratings for coasters available?+
How does `quick_search` differ from `search_coasters` for finding a coaster?+
quick_search is optimized for fast, autocomplete-style lookups and returns a small result set with title, subtitle, and a link path per result — it also covers parks, not just coasters. search_coasters returns a more complete result set with park_id and opened fields, and omitting the query returns all coasters with a total count. Use quick_search for type-ahead UI and search_coasters for full dataset queries.