Cigarbase APIcigarbase.app ↗
Access 50,000+ cigars from Cigarbase. Search by name or brand, retrieve blend details, wrapper type, strength, flavor profiles, tasting notes, and pairing data.
What is the Cigarbase API?
The Cigarbase API gives developers access to a catalog of over 50,000 premium cigars through 2 endpoints. Use search_cigars to find cigars by name or brand with paginated results, or call get_cigar with a UUID to retrieve a full profile including blend composition, flavor radar data, tasting notes, food and spirit pairings, market data, and aging potential.
curl -X GET 'https://api.parse.bot/scraper/d2b1d5c3-de44-441a-b093-90e6de5a8a38/search_cigars?query=Bolivar' \ -H 'X-API-Key: $PARSE_API_KEY'
Search cigars by name or brand. Returns paginated results matching the query against cigar names and brand names. Each result includes identification details, blend composition, strength, flavor profile, and rating. One upstream request per call; use offset/limit for pagination.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return per page. Clamped to 100. |
| queryrequired | string | Search term matched against cigar name and brand name (case-insensitive substring match). |
| offset | integer | Number of results to skip for pagination. |
{
"type": "object",
"fields": {
"limit": "The limit that was applied",
"query": "The search term that was used",
"total": "Total number of matching cigars across all pages (integer or null)",
"cigars": "Array of cigar objects matching the query, each with id, name, brand, origin, strength, wrapper, binder, filler, color, shape, vitola, ring_gauge, length, description, tasting_notes, flavor_profile, flavor_radar, rating, production_method, limited_edition, and image_url",
"offset": "The offset that was applied"
},
"sample": {
"data": {
"limit": 20,
"query": "Padron 1964",
"total": 7,
"cigars": [
{
"id": "ba227f42-92dc-474d-96af-0061b5f08f46",
"name": "Padron 1964 Anniversary Maduro Gift Pack (5)",
"brand": "Padron 1964 Anniversary Maduro",
"color": null,
"shape": null,
"binder": "Nicaraguan Habano",
"filler": "Nicaraguan",
"length": "5.0",
"origin": "Nicaragua",
"rating": null,
"vitola": "Robusto",
"wrapper": "Undisclosed",
"brand_id": "ed89fe9b-f68f-460f-9958-2dd61006669e",
"strength": "Full",
"image_url": "https://images.famous-smoke.com/image/upload/c_lpad,dpr_2.0,f_auto,h_565,q_auto,w_565/v1/skupics/pam/ci-pam-sam.jpg?_i=AB",
"ring_gauge": "50",
"description": "The Padron 1964 Anniversary Maduro is a rich, full-bodied cigar with a complex profile, offering notes of dark chocolate, coffee, and spice.",
"brand_origin": null,
"flavor_radar": {
"wood": 20,
"earth": 20,
"nutty": 5,
"spice": 10,
"sweet": 70,
"leather": 30
},
"tasting_notes": [
"dark chocolate",
"coffee",
"spice",
"leather",
"black cherry"
],
"flavor_profile": [
{
"name": "dark chocolate",
"percentage": 60
}
],
"limited_edition": false,
"production_method": "handmade"
}
],
"offset": 0
},
"status": "success"
}
}About the Cigarbase API
Search and Identify Cigars
The search_cigars endpoint accepts a required query string and performs a case-insensitive substring match against cigar names and brand names. Results are paginated via offset and limit (capped at 100 per page). Each cigar object in the response includes id, name, brand, origin, strength, wrapper, binder, filler, color, shape, and vit. The total field indicates how many matching cigars exist across all pages, enabling you to calculate page counts client-side.
Full Cigar Profiles
Once you have a cigar's UUID from search results, get_cigar returns the complete record. In addition to the core identification fields (brand_id, brand_origin, shape, color), the response includes structured flavor profile data with radar chart values, detailed tasting notes, and pairing suggestions broken into foods, spirits, and beverages. Physical specifications, aging potential, and market data are also present in the returned cigar object.
Blend Composition
Both endpoints expose the full blend breakdown: wrapper, binder, and filler fields describe the leaf composition of each cigar. The strength field provides a rating (e.g., medium, full) that is useful for filtering or building recommendation logic on top of the catalog. These fields are available at the search result level, so you do not need a separate lookup to access blend basics.
The Cigarbase API is a managed, monitored endpoint for cigarbase.app — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when cigarbase.app 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 cigarbase.app 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 cigar recommendation engine filtered by strength and wrapper type.
- Populate a retail product catalog with blend composition and origin data from search results.
- Create food and drink pairing guides using the pairings fields returned by get_cigar.
- Display tasting notes and flavor radar data on a review or rating platform.
- Support a cigar aging tracker by storing aging potential data from full cigar profiles.
- Enable search autocomplete for a cigar shop using the query and brand fields from search_cigars.
- Generate structured product pages using shape, color, filler, binder, and wrapper fields.
| 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.
Does Cigarbase have an official developer API?+
What does get_cigar return beyond what search_cigars already includes?+
How does pagination work in search_cigars?+
offset to skip results and limit (max 100) to control page size. The total field in the response gives the full count of matching records, which can be null for some queries. Each call counts as one upstream request regardless of the limit used.