This site provides a UI for searching for motors and downloading data right within any web browser.
However, for those intrepid souls who would like to integerate the data provided by this site into programs
(such as flight simulators), an API is provided.
Normal users of the site can just ignore this page.
The API described on this page provides basic database access through REST endpoints. Inputs can be specified as XML, JSON or form data and results can be returned as XML or JSON. The v1 API, described on this page, is a superset of the XML-only API supported by the v2 site. The "compatible endpoints" listed are those that were supported by the v2 site.
There are five actions supported, all of which use HTTP POST methods:
There is a OpenAPI (Swagger) spec for API and you can use
to explore the API with it.
Point Swagger Insector (or similar OpenAPI tool) at
Each API is described in its own section below, plus there are a few example programs at the bottom.
The metadata API doesn't return stats or data on individual motors, but instead is used to find out what actual criteria exist for doing a search.This is useful for building interactive programs that want to populate a set of combo boxes with valid search criteria, without hard-coding the actual values into the program. The simplest case is to return metadata encompasing all motors in the database using no input at all: /api/v1/metadata.json (or metadata.xml).
However, its usually desirable to get metadata only for the motors that the user of the API is actually interested in. For example, if you don't care about motors that are out of production, restricting the metadata to available motors makes more sense: /api/v1/metadata.json?availability=available. This endpoint accepts the same query as the search endpoint below.
The search API is where it starts to get more interesting. This is the first API that requires inputs and returns data on specific motors in the the database. This API could be used to drive you own search front-end.