kvraudio.com APIwww.kvraudio.com ↗
Search and browse KVR Audio's plugin database via API. Get developer, category, price, formats, and OS data for VST plugins, instruments, and effects.
curl -X GET 'https://api.parse.bot/scraper/86bc4092-8ea5-48e6-8c49-f02950f1b5de/search_plugins?query=compressor' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for audio plugins by keyword. Returns up to 20 matching products from the first page with developer, category, price, and platform info.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. 'reverb', 'synthesizer', 'compressor') |
| sort_by | string | Sort order for results. Accepted values: 'best-match', 'newest', 'oldest', 'most-popular', 'least-popular' |
{
"type": "object",
"fields": {
"query": "search keyword used",
"sort_by": "sort order applied",
"products": "array of product objects with name, url_slug, kvr_id, category, developer, price, formats, and os",
"page_info": "pagination indicator such as 'Page 1 of 40'",
"total_results": "number of products returned on this page"
},
"sample": {
"data": {
"query": "compressor",
"sort_by": "best-match",
"products": [
{
"os": [
"macOS",
"Windows",
"Linux"
],
"name": "Compressor",
"price": "0",
"kvr_id": "30967",
"formats": [
"VST",
"VST3",
"Audio Unit"
],
"category": "Compressor",
"url_slug": "compressor-by-socalabs",
"developer": "SocaLabs"
}
],
"page_info": "Page 1 of 40",
"total_results": 20
},
"status": "success"
}
}About the kvraudio.com API
The KVR Audio API gives developers programmatic access to thousands of audio plugin listings across 3 endpoints. Use search_plugins to query the KVR product database by keyword, list_plugins to browse by category slug, and get_product_details to retrieve full product records including plugin formats, supported operating systems, developer name, price, and description for any individual title.
What the API Returns
Each product object across all three endpoints includes a consistent set of fields: name, url_slug, kvr_id, category, developer, price, formats, and os. The formats array covers plugin standards such as VST, VST3, AU, AAX, and CLAP. The os field lists supported platforms (Windows, macOS, Linux). Prices are returned as strings when listed by the developer, or null when not publicly disclosed.
Searching and Browsing
search_plugins accepts a required query string and an optional sort_by parameter with five accepted values: best-match, newest, oldest, most-popular, and least-popular. Results are scoped to the first page (up to 20 products) and include a page_info string such as Page 1 of 40 and a total_results count for the current page. list_plugins works the same way but takes a category slug drawn directly from KVR's URL structure — for example reverb, the-newest-plugins, or most-popular-audio-software — making it straightforward to mirror any KVR browse page.
Product Detail Records
get_product_details takes a slug value from the url_slug field returned by the other two endpoints and returns the full product record. This adds a description text block, a developer_slug for linking to the developer's KVR page, and a category path string in addition to the core fields. The image field provides a direct URL to the product's thumbnail. This endpoint is the right choice when you need the product description or want to confirm format and OS support before presenting a recommendation.
- Build a plugin discovery tool that filters results by format (VST3, AU, AAX) and OS using the
formatsandosfields. - Aggregate pricing data across plugin categories by querying
list_pluginswith category slugs and collecting thepricefield. - Track newly released plugins by sorting
search_pluginsresults withsort_by: neweston a scheduled basis. - Compile a developer catalog by extracting
developeranddeveloper_slugvalues across category pages. - Power a plugin recommendation engine that matches user-entered keywords to KVR products via
search_plugins. - Enrich an internal music software database with plugin descriptions and category paths from
get_product_details. - Monitor the most popular plugins in a given category using
list_pluginswithmost-popular-audio-softwareor similar slugs.
| 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 | 250 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 KVR Audio have an official developer API?+
What does `get_product_details` return that the search and list endpoints don't?+
get_product_details adds a description text block, a developer_slug for constructing KVR developer page URLs, and a direct image URL to the product thumbnail. The core fields — name, price, formats, os, category, and developer — are present across all three endpoints, but the description and image fields are only available in the detail endpoint.Does the API return results beyond the first page of search or category results?+
page_info field (e.g. Page 1 of 40) indicates how many pages exist, but pagination is not yet supported. You can fork this API on Parse and revise it to add page offset or cursor parameters to retrieve subsequent pages.Can I retrieve user reviews or ratings for a plugin?+
How should I get the `slug` value needed for `get_product_details`?+
url_slug field is returned in every product object from both search_plugins and list_plugins. Pass that value directly as the slug parameter to get_product_details. For example, a search for 'compressor' might return a product with url_slug: 'gem-comp160-by-overloud', which you then use to fetch the full record.