Versioning
This page is outdated. Please go to our new documentation under https://docs.fulfillmenttools.com/documentation.
Our API is considered versionless. That means, that our API evolves in a backwards compatible way. The following changes however are considered to be backwards-compatible:
Adding new API resources.
Adding new optional request parameters to existing API methods.
Adding new properties to existing API responses.
Changing the order of properties in existing API responses.
Adding values to enum fields
Outside of these backwards compatible changes we might mark an endpoint or data models with the Beta-Flag in order to make transparent that this specific endpoint might be subject to change (please read more on the Beta-Flag here).
Last updated