Discover/Cure Hydration API
live

Cure Hydration APIcurehydration.com

Access Cure Hydration's product catalog via API. Browse collections, list electrolyte drink products, retrieve variants and pricing, and search by keyword.

This API takes change requests — .
Endpoint health
verified 3h ago
list_collections
list_products
get_product
search_products
4/4 passing latest checkself-healing
Endpoints
4
Updated
4h ago

What is the Cure Hydration API?

The Cure Hydration API provides 4 endpoints for accessing the Cure Hydration electrolyte drink mix catalog, including product listings, collection browsing, detailed product data, and keyword search. The get_product endpoint returns full variant-level detail — SKU, weight, pricing, availability, and HTML description — for any product handle. The list_collections endpoint exposes the full set of collection handles needed to filter product queries by category.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

api.parse.bot/scraper/57c86074-a038-4582-8bad-faecf70b5e94/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/57c86074-a038-4582-8bad-faecf70b5e94/list_collections' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 4 totalmissing one? ·

List all product collections available on the Cure Hydration store. Returns collection metadata including title, handle, and timestamps. Collections can be used as input to list_products.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "count": "integer total number of collections returned",
    "collections": "array of collection objects with id, title, handle, description, published_at, updated_at"
  },
  "sample": {
    "data": {
      "count": 22,
      "collections": [
        {
          "id": 269624279219,
          "title": "Hydration",
          "handle": "hydration",
          "updated_at": "2026-08-24T07:07:57-04:00",
          "description": null,
          "published_at": "2021-05-24T12:53:44-04:00"
        },
        {
          "id": 269625262259,
          "title": "Energy",
          "handle": "energy",
          "updated_at": "2026-08-24T07:07:57-04:00",
          "description": null,
          "published_at": "2021-05-24T13:02:25-04:00"
        }
      ]
    },
    "status": "success"
  }
}

About the Cure Hydration API

Collections and Product Browsing

The list_collections endpoint returns all product collections available in the Cure Hydration store, including each collection's id, title, handle, description, published_at, and updated_at. Collection handles (for example hydration, energy, or kids) can be passed directly to the list_products endpoint via its collection parameter to scope results to a specific product grouping.

Listing and Paginating Products

list_products accepts optional page and limit parameters (up to 250 per page) alongside a collection handle. Each product in the response includes id, title, handle, product_type, vendor, tags, price_min, variants, images, and published_at. This makes it straightforward to iterate the full catalog or focus on a single collection.

Detailed Product Data

get_product takes a handle slug — obtainable from list_products or search_products — and returns the complete product record. Response fields include the full variants array (each with price, compare_at_price, sku, barcode, weight, weight_unit, and available), all product options with their values, an array of images, and an HTML description. The compare_at_price field makes it possible to detect sale pricing at the variant level.

Keyword Search

search_products accepts a required query string and an optional limit (max 10). Results include per-product price_min, price_max, available, image, and a direct url to the product page. This endpoint is suited for autocomplete or quick-lookup workflows where the caller knows part of a product name or flavor.

Reliability & maintenanceVerified

The Cure Hydration API is a managed, monitored endpoint for curehydration.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when curehydration.com 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 curehydration.com 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.

Last verified
3h ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a product comparison tool that pulls variant-level pricing and availability from get_product for multiple SKUs.
  • Sync Cure Hydration's catalog into a third-party inventory or PIM system using list_products with pagination.
  • Detect sale products by comparing price against compare_at_price in the variants array returned by get_product.
  • Populate a storefront or affiliate site with collection-organized product listings using list_collections and list_products.
  • Implement a flavor-search autocomplete using search_products with a keyword query like 'lemon' or 'berry'.
  • Track product additions and updates over time by comparing published_at and updated_at fields across catalog snapshots.
  • Filter the kids-specific product line by passing the kids collection handle to list_products.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does Cure Hydration have an official developer API?+
Cure Hydration does not publish a documented public developer API. Their store runs on Shopify, which exposes some public JSON endpoints by convention, but there is no official API program, documentation, or authentication key system offered by Cure Hydration directly.
What does `get_product` return that `list_products` does not?+
list_products returns summary-level data suitable for browsing: price_min, a variants array, and images. get_product returns the full variant record per SKU — including sku, barcode, weight, weight_unit, compare_at_price, and the complete HTML description. If you need inventory-level or fulfillment details per variant, get_product is the right call.
How does pagination work in `list_products`?+
The endpoint accepts page (integer, default 1) and limit (integer, max 250) parameters. Each response includes the current page number and a count of products returned. To retrieve all products in a collection, increment the page parameter until count is less than the requested limit.
Does the API return customer reviews or ratings for products?+
Not currently. The API covers product metadata, variant pricing, availability, images, and descriptions. Customer reviews and star ratings are not included in any of the four endpoints. You can fork this API on Parse and revise it to add a reviews endpoint if that data is needed.
Does `search_products` support filtering by collection or product type?+
Currently search_products only accepts a query string and an optional limit. It does not support filtering results by collection handle or product type within the same call. The API covers collection-scoped browsing through list_products with the collection parameter instead. You can fork this API on Parse and revise it to add collection-aware filtering to the search endpoint.
Page content last updated . Spec covers 4 endpoints from curehydration.com.