getfpv.com APIgetfpv.com ↗
Access GetFPV's FPV drone parts catalog via API. Search products, browse categories, get specs, pricing, and stock status for motors, flight controllers, and more.
curl -X GET 'https://api.parse.bot/scraper/c2e4196d-34d8-49cb-ab61-e02e70e36676/search_products?limit=3&query=motor' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products by keyword across all categories. Returns product listings with name, SKU, price, stock status, and more. Results are paginated.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (zero-indexed) |
| limit | integer | Max results per page |
| queryrequired | string | Search keyword |
{
"type": "object",
"fields": {
"products": "array of product objects with name, sku, price, stock_status, stock_qty, url, thumbnail, brand, and categories",
"total_hits": "integer total matching products",
"total_pages": "integer total pages available",
"current_page": "integer current page number (zero-indexed)"
},
"sample": {
"data": {
"products": [
{
"sku": "22354",
"url": "https://www.getfpv.com/dys-f722-flight-controller-icm42688p-30x30.html",
"name": "DYS F722 Flight Controller - ICM42688P - 30x30",
"brand": "DYS",
"price": 51.99,
"stock_qty": 6,
"thumbnail": "https://cdn-v2.getfpv.com/media/catalog/product/cache/ad237c46d531aabdb51b70c3aca03811/d/y/dys-f722-flight-controller---icm42688p---30x30-_image-1_.jpg",
"categories": {
"level0": [
"Electronics"
],
"level1": [
"Electronics /// Flight Controllers"
]
},
"stock_status": "In Stock"
}
],
"total_hits": 943,
"total_pages": 189,
"current_page": 0
},
"status": "success"
}
}About the getfpv.com API
The GetFPV API provides 7 endpoints for querying the GetFPV drone components catalog, covering search, category browsing, and detailed product data. Use search_products to find parts by keyword and receive structured results including SKU, price, stock status, stock quantity, brand, and thumbnail URL. Dedicated endpoints for flight controllers, motors, new arrivals, and sale items make it straightforward to target specific segments of the catalog without custom category filtering.
Product Search and Category Browsing
The search_products endpoint accepts a required query string and returns paginated arrays of product objects, each containing name, sku, price, stock_status, stock_qty, url, thumbnail, brand, and categories. Pagination is zero-indexed via the page parameter, and total_hits and total_pages fields let you iterate through full result sets. The get_category_products endpoint accepts a category string that supports multi-level paths using /// as a separator — for example, Electronics /// Flight Controllers — so you can target nested subcategories directly.
Convenience Category Endpoints
Four endpoints target specific catalog segments without requiring you to know the category path: get_flight_controllers (maps to Electronics /// Flight Controllers), get_motors (maps to Motors), get_new_products (maps to the New Products listing), and get_sale_products (maps to the On Sale listing). All four share the same paginated response shape as search_products, making it trivial to swap between them in a single code path.
Product Detail Data
The get_product_details endpoint accepts either a full product URL or a slug path (e.g., product-name.html) and returns a richer object: sku, name, brand, price formatted as USD <amount>, an images array of URLs, a description string, stock_status, and a specifications object of key-value pairs. The specifications object reflects product-level technical attributes such as dimensions, weight, or compatibility data as listed on the product page — the actual keys vary by product type.
Pagination and Data Shape Notes
All listing endpoints use zero-indexed pagination. The limit parameter controls page size. Stock status on listing endpoints is a string (In Stock or Out of Stock), and stock_qty gives a numeric quantity where available. Price in listing responses is a formatted string, consistent with the price field in get_product_details.
- Monitor stock availability for FPV motors and flight controllers to trigger restock alerts using
stock_statusandstock_qty. - Build a price comparison tool for FPV components by querying
search_productsand extractingpriceandbrandfields. - Aggregate new product arrivals via
get_new_productsto power a weekly newsletter or catalog update feed. - Scrape technical specifications from
get_product_detailsto populate a parts database with dimensions, weights, and compatibility data. - Track sale inventory over time using
get_sale_productsto identify which categories GetFPV discounts most frequently. - Populate an affiliate storefront with product names, thumbnails, URLs, and prices from category-specific listing endpoints.
- Filter the FPV parts catalog by multi-level category using
get_category_productswith///path notation for precise subcategory targeting.
| 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 GetFPV have an official developer API?+
What does `get_product_details` return that the listing endpoints don't?+
get_product_details adds a specifications object with product-level key-value attributes (varies by product type), a full images array, and a description string. Listing endpoints return thumbnail only and omit specifications and descriptions entirely.How does category path filtering work in `get_category_products`?+
category parameter accepts either a top-level name like Motors or a slash-delimited path using /// as the separator, such as Electronics /// Flight Controllers. Omitting the parameter entirely returns all products across categories, paginated.Are customer reviews or ratings available through this API?+
Does the API expose variant or option data for products that come in multiple configurations?+
get_product_details returns a single price, stock_status, and specifications object without breaking out individual variants or options. You can fork it on Parse and revise to add variant-level data for products with multiple size or configuration options.