Monster Energy APImonsterenergy.com ↗
Retrieve Monster Energy drink data for New Zealand: names, flavour profiles, sugar/caffeine levels, serving sizes, and transparent can images via 2 endpoints.
What is the Monster Energy API?
The Monster Energy NZ API provides 2 endpoints to browse and look up Monster Energy drinks available in New Zealand, returning up to 9 fields per product including name, flavour profile, description, sugar and caffeine content, serving size, and a transparent .webp can image URL. Use list_drinks to retrieve the full catalogue with optional category filtering, or get_drink to fetch a single product by its slug.
curl -X GET 'https://api.parse.bot/scraper/76d65545-6071-4ce2-8c4f-9df3cd6915d8/list_drinks?category=monster-energy' \ -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 monsterenergy-com-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: Monster Energy NZ SDK — bounded, re-runnable; every call capped."""
from parse_apis.monsterenergy_com_api import MonsterEnergy, Category, DrinkNotFound
client = MonsterEnergy()
# List all drinks, capped at 3
for drink in client.drinks.list(limit=3):
print(drink.name, drink.flavor_profile, drink.caffeine, drink.sugar)
# Filter by category
for drink in client.drinks.list(category=Category.JUICE_MONSTER, limit=3):
print(drink.name, drink.can_image_url)
# Get a specific drink by slug and category
item = client.drinks.list(category=Category.MONSTER_ULTRA, limit=1).first()
try:
detail = client.drinks.get(slug=item.slug, category=item.category)
print(detail.name, detail.flavor_profile, detail.description)
except DrinkNotFound as e:
print(f"not found: {e.slug}")
print("exercised: drinks.list, drinks.get")
Retrieve all Monster Energy drinks available in New Zealand with full details including name, flavour profile, description, nutritional info (sugar, caffeine, serving size), and a transparent .webp can image URL. Optionally filter by category. Each drink is fetched individually for complete detail; the full catalog is ~14 items.
| Param | Type | Description |
|---|---|---|
| category | string | Filter by product category slug. |
{
"type": "object",
"fields": {
"total": "integer count of drinks returned",
"drinks": "array of drink objects with full details"
},
"sample": {
"data": {
"total": 14,
"drinks": [
{
"name": "Juice Monster Mango Loco",
"slug": "mango-loco",
"sugar": "60 g",
"caffeine": "150 mg",
"category": "juice-monster",
"description": "Juice Monster's Mango Loco uses real mango juice powered by our energy blend for a refreshing juice with energy.",
"serving_size": "500 ml",
"can_image_url": "https://web-assests.monsterenergy.com/mnst/3f8d5be1-d198-4c68-be7b-735b4bd58c9d.webp",
"flavor_profile": "Juicy Mango"
}
]
},
"status": "success"
}
}About the Monster Energy API
What the API returns
Both endpoints return product data sourced from the Monster Energy New Zealand catalogue. Each drink object includes name, slug, category, description, flavor_profile, sugar, caffeine, serving_size, and can_image_url. Nutritional fields (sugar, caffeine, serving_size) are returned as formatted strings (e.g. '60 g', '150 mg', '500 ml') or null when not listed on the product page.
Endpoints
list_drinks accepts an optional category parameter (a category slug string) to narrow results to a specific product line such as juice-monster or zero-ultra. It returns a total count alongside a drinks array of full drink objects. get_drink requires both a slug (e.g. mango-loco, original-green) and a category slug, and returns the complete detail object for that single product. Slugs needed for get_drink are obtainable from the list_drinks response.
Coverage and scope
The API covers the New Zealand regional catalogue on monsterenergy.com. Product availability, names, and nutritional figures reflect what is published for the NZ market, which may differ from other regional Monster Energy sites. The can_image_url field points to a transparent .webp image suitable for display in product grids or comparison tools.
The Monster Energy API is a managed, monitored endpoint for monsterenergy.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when monsterenergy.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 monsterenergy.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.
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 product catalogue UI displaying Monster Energy cans with their transparent .webp images and flavour profiles
- Compare sugar and caffeine content across all NZ Monster Energy variants using the
sugarandcaffeinefields - Filter products by category slug to display only juice-based or zero-sugar Monster lines
- Populate a nutritional database with serving size, sugar, and caffeine data for energy drink tracking apps
- Generate a product lookup tool that resolves a drink slug to its full description and flavour profile
- Audit which NZ Monster Energy products omit caffeine or sugar disclosures by checking for null nutritional fields
| 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 Monster Energy have an official developer API?+
What does `list_drinks` return and how does the category filter work?+
category parameter, list_drinks returns all available NZ drinks as an array of full drink objects plus a total count. Passing a category string (e.g. juice-monster) limits results to products in that category. Category slugs correspond to the product line sections on the Monster Energy NZ site.Are sugar and caffeine values always present in the response?+
sugar, caffeine, and serving_size fields return null when the product page does not list that information. You should handle null values when building any nutritional comparison logic.