Skip to main content
This reference provides information about the available Quivo API environments, their base URLs, and when to use each environment.

​
Overview

The Quivo API is available in two environments:
  • Production: The live environment for handling real business operations
  • Sandbox: The testing environment for development and integration testing
All API endpoints are available in both environments. Both use the same API structure and authentication flow. Each environment has its own base URL, its own API credentials and its own data.

​
Production Environment

Use the production environment when you are ready to process real orders, need to access live inventory data, are handling actual customer fulfillment requests, and have completed testing in the sandbox environment. Base URL: https://api.quivo.co
The production environment processes real orders and charges. Only use this environment when you are ready to handle live operations.

​
Sandbox Environment

Use the sandbox environment for development, integration testing, learning the Quivo API, validating features without affecting real data, and testing error handling and edge cases before deploying to production. Base URL: https://api-sandbox.quivo.co Web App Sandbox: https://app-sandbox.quivo.co/
Both environments use the same token flow. An API credential belongs to one environment: create it in the web app of the environment you want to call.

​
Using the Base URL

In all API documentation examples, you’ll see ${BASE_URL} used as a placeholder. Replace this placeholder with the appropriate base URL of your environment:
  • Production: Replace ${BASE_URL} with https://api.quivo.co
  • Sandbox: Replace ${BASE_URL} with https://api-sandbox.quivo.co

​
Example

Here’s an example of how to use the base URL in an API request:
For sandbox:

​
Authentication

Both environments use the same authentication method:
  1. Access token: Get an access token from POST ${BASE_URL}/v2/oauth2/token with your API credential.
  2. API calls: Send the token in the Authorization: Bearer header on every call to ${BASE_URL}/v2/....
See the Authentication reference for detailed authentication instructions.
To get an API credential for an environment, create it in that environment’s Connector web app. See Create an API credential.

​
Where to go next

Now that you understand the available environments, continue with these guides:

Authentication

Learn how to authenticate API requests with API credentials and access tokens.

Make your first API call

Step-by-step tutorial for making your first API request to the Quivo API.