Monster Energy APImonsterenergy.com ↗
Access Monster Energy NZ drink data via API: names, flavour profiles, caffeine and sugar levels, serving sizes, and transparent can image URLs.
What is the Monster Energy API?
The Monster Energy NZ API exposes 3 endpoints that return product data for Monster Energy drinks available in New Zealand. The list_drinks endpoint returns the full catalog with up to 9 fields per drink — including name, flavour profile, description, caffeine content, sugar content, serving size, category, slug, and a transparent .webp can image URL. Drinks can be filtered by category, and individual products can be fetched by slug using get_drink.
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.Monster_Energy_NZ_API import MonsterEnergy, Category, DrinkNotFound
client = MonsterEnergy()
# List all available categories
for cat in client.drink_categories.list(limit=3):
print(cat.slug, cat.name)
# List drinks filtered by category
for drink in client.drinks.list(category=Category.MONSTER_ULTRA, limit=3):
print(drink.name, drink.flavor_profile, drink.caffeine)
# Get a specific drink by slug and category
item = client.drinks.list(category=Category.JUICE_MONSTER, limit=1).first()
try:
detail = client.drinks.get(slug=item.slug, category=item.category)
print(detail.name, detail.description, detail.sugar)
except DrinkNotFound as e:
print(f"not found: {e.slug}")
print("exercised: drink_categories.list, 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
Endpoints and Data Coverage
The API covers three operations. list_categories returns all product category slugs and display names from the Monster Energy NZ energy drinks navigation — useful as a starting point for filtering. list_drinks accepts an optional category parameter and returns a total count alongside an array of drink objects, each carrying the same full field set as a single-product lookup. get_drink takes a required slug and category and returns the same fields for one specific product.
Response Fields
Every drink object includes name, slug, category, description, flavor_profile, sugar, caffeine, serving_size, and can_image_url. The sugar and caffeine fields are strings with units (e.g. '60 g', '150 mg') and may be null if not listed for that product. The can_image_url points to a transparent .webp image, suitable for rendering against custom backgrounds. Slugs returned by list_drinks (e.g. mango-loco, zero-ultra) can be passed directly as the slug input to get_drink.
Scope and Limitations
All data reflects the Monster Energy NZ storefront. Products listed in other regional storefronts (US, UK, AU, etc.) are not included. There is no pagination parameter — list_drinks returns all matching products in a single response. Nutritional fields beyond caffeine and sugar (e.g. calories, B-vitamins, taurine) are not returned by any current endpoint.
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?+
- Display a full Monster Energy NZ product catalog with can images and nutritional labels in a beverage discovery app.
- Filter drinks by category slug to build a category-browsing UI using
list_categoriesandlist_drinks. - Render transparent can images from
can_image_urlagainst custom backgrounds for promotional or editorial layouts. - Compare caffeine and sugar levels across products by iterating the
drinksarray fromlist_drinks. - Look up a specific product's flavour profile and description using
get_drinkwith a known slug. - Populate a database of NZ-market energy drinks with structured nutritional data for dietary tracking tools.
- Identify products with null caffeine or sugar values to flag incomplete nutritional data in a compliance workflow.
| 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 Monster Energy have an official public developer API?+
What does `list_categories` return, and how does it relate to the other endpoints?+
list_categories returns a flat array of category objects, each with a slug and name. These slugs are the valid values for the category parameter accepted by both list_drinks (optional filter) and get_drink (required input). Running list_categories first is the reliable way to get current category slugs before querying the other endpoints.Are drinks from Monster Energy's US or other regional sites included?+
Does the API return full nutritional panel data beyond caffeine and sugar?+
caffeine, sugar, and serving_size per drink. Other nutritional values such as calories, taurine, B-vitamins, or sodium are not included in any current endpoint. You can fork the API on Parse and revise it to add an endpoint that captures the extended nutritional panel if those fields are available on the product pages.Can I retrieve drinks without knowing the category upfront?+
category parameter in list_drinks is optional — omitting it returns the full cross-category catalog. For get_drink, however, category is required alongside slug. You can obtain both values from a prior list_drinks call.