The Finale Inventory API is a comprehensive set of services based on REST principles. The API has access to read and modify every entity exposed in the user interface - in fact Finale's user interface uses the API for its operation. The API is exposed using JSON over HTTPS using the GET method for read operations and the POST method for modification operations
To get started using the API first read the documentation on Authentication. All API requests must include an authorization header.
Be sure also to read the documentation on Resource patterns. The Finale Inventory API is defined in terms of resource collections that consistently use a small set of patterns. The documentation on the individual resource collections assumes a foundational understanding of these patterns.
The Example documentation demonstrates how to both read and write using the API using curl, a command line tool that can be used to experiment with the APIs. The curl tool is free software that comes pre-installed on Mac OS X and most Linux distributions and is available for Windows. If you do install curl, select a package the includes SSL support which is required for the Finale Inventory API.
The actual API consists of a set of resource collections corresponding to the various entities exposed in the user interface. The names of the resource collections do not exactly match the names in the user interface. The following list shows the relation between names in the user interface and related resource collections:
- Build ⇒ Work effort
- Customer, Supplier ⇒ Party group
- Location, Sublocation ⇒ Facility
- Product ⇒ Product
- Product lookup ⇒ Scan lookup
- Purchase, Sale ⇒ Order, Shipment
- Stock transfer ⇒ Inventory transfer
- Stock change ⇒ Inventory variance
- View stock ⇒ Inventory item
There are places in the documentation where specific fields or entire resources are marked as undocumented. Generally this is because we haven't had yet had customers expressing interest in using those parts of the API. Please contact us if you need to access those parts of API so we can assist you and improve the documentation.