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

# Jungle Scout API

Jentic publishes the only available OpenAPI specification for Jungle Scout API, keeping it validated and agent-ready. The Jungle Scout API exposes Amazon-marketplace research data used by sellers and analysts to size opportunities, study competitors, and forecast sales. Endpoints return keyword research keyed by ASIN or seed term, historical search-volume time series, product database queries, sales estimates, and share-of-voice metrics. It is best treated as a structured analytics feed for Amazon e-commerce, not a transactional API.

## For AI agents

Pull Amazon keyword research, sales estimates, and share-of-voice data on demand for product and category analysis.

## Scope

Does not handle Amazon order management, listing creation, or payouts - use for Amazon market and keyword research only.

## Capabilities

- Run keyword research keyed by ASIN through POST /api/keywords/keywords_by_asin_query
- Run keyword research keyed by seed keyword through POST /api/keywords/keywords_by_keyword_query
- Pull historical search-volume time series for an Amazon search term via GET /api/keywords/historical_search_volume
- Query the Jungle Scout product database with filters such as category, BSR, and price using POST /api/product_database_query
- Estimate monthly sales for an ASIN with GET /api/sales_estimates_query
- Measure share-of-voice across paid and organic placements with GET /api/share_of_voice

## Use cases

### New Listing Keyword Research

Brands launching a new Amazon ASIN need ranked keyword opportunities tied to a competitor product. POST /api/keywords/keywords_by_asin_query returns search terms a chosen ASIN ranks for, while POST /api/keywords/keywords_by_keyword_query expands a seed term into related queries. Together they replace hours of manual scraping with a single structured pull.

Example prompt: For ASIN 'B07ABC1234', call POST /api/keywords/keywords_by_asin_query and return the top 50 keywords sorted by search volume.

### Category Opportunity Sizing

PE firms and brand aggregators evaluating an acquisition use POST /api/product_database_query to pull every product in a category that matches revenue, BSR, and review thresholds. The response feeds a rollup of TAM and competitive intensity. This shrinks weeklong manual diligence into an automated nightly job.

Example prompt: Call POST /api/product_database_query with category 'Home & Kitchen', min_revenue=10000, max_reviews=500 and aggregate total monthly revenue across results.

### Brand Share-of-Voice Tracking

Marketing teams want a weekly read on how often their brand appears in Amazon search results for high-intent terms. GET /api/share_of_voice returns paid and organic placement share for a keyword set, which the team trends over time. This produces a board-ready chart without manual screenshotting of Amazon SERPs.

Example prompt: For the keyword list ['organic dog food','grain free dog food'], call GET /api/share_of_voice weekly and store paid and organic share for the brand 'Acme'.

### Agent-Powered Listing Audit

An AI merchandising assistant audits a portfolio of ASINs by combining sales estimates and keyword coverage. Through Jentic, the agent calls /api/sales_estimates_query for each ASIN and /api/keywords/keywords_by_asin_query for missing keywords, producing a prioritised optimisation list. This puts a Jungle Scout-grade audit behind a chat prompt.

Example prompt: Through Jentic, search 'sales estimates for an Amazon ASIN', load GET /api/sales_estimates_query, execute for ASINs ['B07A','B07B','B07C'], then summarise underperformers.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/keywords/keywords_by_asin_query | Keyword research keyed by ASIN |
| POST | /api/keywords/keywords_by_keyword_query | Keyword research keyed by seed term |
| GET | /api/keywords/historical_search_volume | Historical search-volume time series |
| POST | /api/product_database_query | Filterable product database query |
| GET | /api/sales_estimates_query | Monthly sales estimate for an ASIN |
| GET | /api/share_of_voice | Share-of-voice metrics for keywords |

## Key resources

- **Keywords** — Keyword research by ASIN or seed term and historical search-volume time series
- **Product Database** — Filterable lookup over the Jungle Scout product database
- **Sales Estimates** — Monthly sales estimates for a given ASIN
- **Share of Voice** — Paid and organic share-of-voice metrics for keywords

## Why Jentic

- **Setup:** Wiring the Jungle Scout API by hand means learning its API key auth, shaping the keyword and product database query payloads, and parsing research results yourself. Through Jentic you install once, import the Jungle Scout API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Jungle Scout addresses its research queries by request payload and query parameters rather than a resource id in the path, so you limit the agent to the operations it needs, such as fetching a sales estimate or keyword data. Operations like the product database query are left out unless you include them.
- **Credential handling:** Your Jungle Scout API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'sales estimate for an Amazon ASIN' or 'keywords by ASIN', 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

- **Ahrefs API** — Web search keyword and backlink data, broader than Amazon-only research.
- **Semrush API** — General-web keyword and competitive research that overlaps with Jungle Scout outside Amazon.
- **Shopify Admin API** — Combine Jungle Scout demand signals with Shopify storefront execution.

## FAQ

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

Jungle Scout does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 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 Jungle Scout API uses an API key passed in the Authorization header. Through Jentic the key sits in the encrypted vault, so the agent runtime only ever holds a scoped session reference.

### Can I get sales estimates for a specific ASIN?

Yes. GET /api/sales_estimates_query returns monthly sales estimates for a given ASIN and marketplace, suitable for category sizing or single-ASIN performance review.

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

Jungle Scout enforces per-plan rate and quota limits negotiated with the developer account; the spec itself does not pin a fixed value. Cache results aggressively and batch ASIN inputs where the endpoint supports arrays.

### How do I run keyword research with the Jungle Scout API through Jentic?

Search Jentic for 'amazon keyword research by asin', load POST /api/keywords/keywords_by_asin_query, and execute with the target ASIN. Jentic returns the matching keywords and their search-volume data.

### Can I pull historical search-volume trends?

Yes. GET /api/keywords/historical_search_volume returns a time-series of search volume for a given Amazon search term, which is useful for seasonality and trend detection.

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

Yes. Because you run Jentic One yourself, your own rules decide which Jungle Scout operations and credentials the agent may use. Jungle Scout addresses each research query by request payload and query parameters rather than a resource id in the path, so you can allow only the operations the agent needs, such as GET /api/sales_estimates_query for sales estimates or POST /api/keywords/keywords_by_asin_query for keyword data. Broader operations like POST /api/product_database_query stay out of reach unless you choose to include them.