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. The only difference is the base URL you use to make requests.

​
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/
API Key Requirement: To access the Sandbox API, you still need an API Key provided by Quivo. The preceding credentials allow access to the Sandbox Web App, but the API requires an additional API Key in the X-Api-Key header.

​
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: 
curl -X GET "https://api.quivo.co/sellers" 
  -H "X-Api-Key: <YOUR_API_KEY>" 
  -H "Authorization: <YOUR_SESSION_TOKEN>"
For sandbox: 
curl -X GET "https://api-sandbox.quivo.co/sellers" 
  -H "X-Api-Key: <YOUR_API_KEY>" 
  -H "Authorization: <YOUR_SESSION_TOKEN>"

​
Authentication

Both environments require the same authentication method:
  1. API Key: Include your API Key in the X-Api-Key header
  2. Session Token: Obtain a session token via POST /login and include it in the Authorization header
See the Authentication reference for detailed authentication instructions.
To obtain API Keys for the environments you need to access, you can request them through The Connector web app (UI) or via the API.

​
Where to go next

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

Authentication

Learn how to authenticate API requests with API keys and session tokens.

Make your first API call

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