canonical: https://jentic.com/apis/developer.junglescout.com/junglescout

# Jungle Scout API V1

Jentic publishes the only available OpenAPI specification for the Jungle Scout API V1, keeping it validated and agent-ready. Jungle Scout exposes Amazon marketplace research data - keyword search volume, ASIN keyword maps, product database queries, sales estimates, and share of voice - as REST endpoints for sellers, brands, and analysts. The six endpoints under /api/keywords, /api/product_database_query, /api/sales_estimates_query, and /api/share_of_voice are gated behind an Authorization header in the format key_name:api_key issued from the Jungle Scout developer dashboard.

## For AI agents

Pull Jungle Scout's Amazon research data - keywords by ASIN, historical search volume, product database, sales estimates, and share of voice - through 6 endpoints.

## Scope

Does not place ads, list products, or operate Amazon Seller Central - use for Amazon keyword, product, sales-estimate, and share-of-voice research only.

## Capabilities

- Pull keywords driving traffic to a given ASIN via POST /api/keywords/keywords_by_asin_query
- Expand a seed keyword into related Amazon keywords via POST /api/keywords/keywords_by_keyword_query
- Read historical search volume for keywords via GET /api/keywords/historical_search_volume
- Query the Jungle Scout product database with filters via POST /api/product_database_query
- Estimate sales for an ASIN via GET /api/sales_estimates_query
- Measure share of voice for a brand or keyword on Amazon via GET /api/share_of_voice
- Authenticate every call with an Authorization header in the form key_name:api_key issued from the Jungle Scout dashboard

## Use cases

### ASIN keyword reverse engineering

Sellers and PPC agencies can reverse-engineer a competitor ASIN by calling POST /api/keywords/keywords_by_asin_query, then enrich the result with GET /api/keywords/historical_search_volume to see seasonality and sustained demand. The combination tells the seller which keywords are worth bidding on or optimising listing copy for, sourced from Jungle Scout's Amazon panel rather than browser scraping.

Example prompt: POST /api/keywords/keywords_by_asin_query with body {asins:['B0BXYZ1234'], marketplace:'us'}, then GET /api/keywords/historical_search_volume for the top 20 returned keywords.

### Niche discovery via product database

Brand managers can use POST /api/product_database_query with filters such as category, monthly sales, price range, and review count to surface high-margin niches. The response is structured product data with sales velocity and competitive intensity hints, suitable for ranking opportunities before product development. This is faster than scraping search result pages and respects Jungle Scout's licensed data.

Example prompt: POST /api/product_database_query with filters {category:'Home & Kitchen', min_monthly_sales:500, max_reviews:200, marketplace:'us'} to find low-competition, high-velocity niches.

### Brand share of voice tracking

Brands can monitor share of voice for their priority keywords through GET /api/share_of_voice, comparing organic and sponsored real estate against competitors. Pair with /api/sales_estimates_query for an ASIN to translate share of voice into estimated revenue impact. This lets a marketing team brief leadership with weekly or monthly snapshots without manual SERP scraping.

Example prompt: GET /api/share_of_voice?keyword=robot+vacuum&marketplace=us and store the per-brand percentages weekly to chart trend.

### Agent-driven Amazon market research

An AI agent supporting a brand team can answer 'What keywords are competitors winning on for X product?' or 'What's the estimated sales for ASIN Y?' by routing through Jungle Scout via Jentic. Jentic returns the operation schema and runs the request with the Authorization header from the vault, so the team's API key never enters the agent's context.

Example prompt: Through Jentic, search 'estimate Amazon sales for an ASIN', load the /api/sales_estimates_query operation, and execute with the ASIN and marketplace parameters.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/keywords/keywords_by_asin_query | Find keywords for a given ASIN |
| POST | /api/keywords/keywords_by_keyword_query | Expand a seed keyword |
| GET | /api/keywords/historical_search_volume | Read historical keyword volume |
| POST | /api/product_database_query | Query the Jungle Scout product database with filters |
| GET | /api/sales_estimates_query | Estimate sales for an ASIN |
| GET | /api/share_of_voice | Measure share of voice on Amazon |

## Key resources

- **Keywords** — ASIN-to-keyword and keyword-to-keyword expansion plus historical volume via /api/keywords/*.
- **Product Database** — Filterable Amazon product database query via POST /api/product_database_query.
- **Sales Estimates** — Sales estimate by ASIN via GET /api/sales_estimates_query.
- **Share of Voice** — Brand and keyword share-of-voice metrics via GET /api/share_of_voice.

## Why Jentic

- **Setup:** Wiring the Jungle Scout API by hand means composing the Authorization header from your key_name and api_key and handling the query payloads for each research call yourself. Through Jentic you install once, import the Jungle Scout API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** You choose which Jungle Scout operations the agent may call, so you can limit it to the ones it needs, such as keywords by ASIN and sales estimates, and leave the product database or share of voice queries out unless you add them. Every operation is research-only, so the agent cannot list products or place ads.
- **Credential handling:** Your Jungle Scout key_name and api_key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find Amazon keywords for an ASIN' or 'estimate Amazon sales', and Jentic returns the matching Jungle Scout operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Semrush API** — SEO and SEM analytics for Google search alongside Amazon research.
- **Amazon SP-API Orders** — Amazon Selling Partner API for retrieving real seller orders.
- **NewsAPI.org** — Aggregated news data - different domain, but useful for trend signal.

## FAQ

### Why is there no official OpenAPI spec for the Jungle Scout API?

Jungle Scout publishes a developer portal at developer.junglescout.com but does not publish a single OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Jungle Scout API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Jungle Scout API use?

The API uses an Authorization header in the format key_name:api_key, both issued from the Jungle Scout developer dashboard. There is no OAuth flow. Through Jentic, the key_name and api_key are stored encrypted in the vault and the Authorization header is set at execution time, so the raw credentials never reach the agent.

### Can I find competitor keywords for an ASIN through this API?

Yes. POST /api/keywords/keywords_by_asin_query with the ASIN list and marketplace returns the keywords driving traffic to those products. Pair with GET /api/keywords/historical_search_volume to see how those keywords trend over time before deciding what to bid on.

### What are the rate limits for the Jungle Scout API?

The OpenAPI spec does not declare rate limits explicitly. Jungle Scout enforces per-key throughput on developer plans; treat HTTP 429 as a signal to back off and refer to your developer dashboard for the limits attached to your plan tier.

### How do I estimate Amazon sales for an ASIN through Jentic?

Through Jentic, search 'estimate Amazon sales for an ASIN', load the Jungle Scout /api/sales_estimates_query operation, and execute with the ASIN and marketplace parameters. Jentic injects the Authorization header from the vault.

### Does the Jungle Scout API cover non-US Amazon marketplaces?

Yes. Most operations accept a marketplace parameter so you can run queries against Amazon US, UK, DE, JP, and other supported marketplaces. The set of supported marketplaces is governed by your Jungle Scout subscription and panel coverage rather than the API spec itself.

### Can I limit what my agent is allowed to do with the Jungle Scout API?

Yes. Jentic One is self-hosted, so you set the rules that decide which of the six Jungle Scout operations your agent can call and which credentials it may use. You can allow only what a task needs, such as keywords by ASIN (POST /api/keywords/keywords_by_asin_query) and sales estimates (GET /api/sales_estimates_query), and leave the product database or share of voice queries out until you choose to add them. Every Jungle Scout operation is research-only, so even a fully enabled agent cannot list products or place ads.