Downloads
Download Postman collections, environment files, and other resources to get started with the SpendOne Platform API.
Postman Collections
API Collection
Download the complete SpendOne Core API collection for Postman:
📥 Download SpendOne Core API Collection
The collection is generated from the OpenAPI specification on every documentation deploy, so it covers every operation the API serves, grouped into the same folders as the API reference.
Two things it does not carry: request bodies are schema templates (<string>, <number>) rather than worked examples, and response examples are left out to keep the import small. The reference has both.
Environment Files
Choose the appropriate environment file for your setup:
Local Development
Use a Postman environment you define locally (for example base_url pointing at your API). A shared local environment file is not published from this repository.
Staging Environment
📥 Download Staging Environment
Use this environment for testing against the staging environment.
Production Environment
📥 Download Production Environment
Use this environment for production API calls.
OpenAPI Specifications
Swagger JSON
The OpenAPI 2.0 specification in JSON format.
Swagger YAML
The same specification in YAML format.
Both are the published integration surface, the same document the API reference and the Postman collection above are generated from: operations that only serve SpendOne's own clients or the platform's operation are filtered out of it. Generate your client from this file rather than from a hand-maintained copy.
Getting Started with Postman
1. Import the Collection
- Open Postman
- Click Import in the top left
- Select the downloaded
SpendOne-Core-API.postman_collection.jsonfile - Click Import
2. Import Environment Files
- In Postman, click the Environments tab
- Click Import
- Select the appropriate environment file for your setup
- Click Import
3. Configure Your Environment
The collection references three variables:
base_url: the API host for the environment, without the/api/v1suffix; every request adds that path itselfauth_token: your bearer token; see API Basics for how to obtain oneuser_code: the calling user's code, prefilled on requests that address a user
base_url and auth_token are all you need for a first authenticated request. The tenant is taken from the token's tenant_id claim, so there is no tenant variable to set.