First steps / Account
Envia.com sandbox environment
Envia.com sandbox environment is a safe space where you can experiment with all the features of the platform without affecting your real operations. It is ideal to familiarize yourself with the system before you start sending packages with real money.
What is it for?
- Test the quotation, generation and cancellation of guides at no additional cost.
- Connect and verify your ecommerce stores before activating them in production.
- Allow your staff to practice and get to know the platform.
- Make sure everything is working properly before launching your operations.
Differences between sandbox and production environment
| Sandbox environment | Production environment |
|---|---|
| Fictitious data | Actual data |
| No real costs | Charges to your balance |
| For experimentation | For actual operations |
ℹ️ The sandbox environment does not affect your actual balance nor does it generate charges to your accounts.
Access the test environment
Log in to your Envia.com account.
2. In the side menu, click on Developers > Testing Environment.
3. A new tab will open in accounts-sandbox.envia.com with the test environment's login screen.
4. Create a test account with a new username and password, or log in if you already have one.
5. Once inside, you'll be in shipping-test.envia.com, the test environment dashboard.
ℹ️ Your production account credentials do not work in the test environment. Even if you log in using your live account, you must register separately.
Get the API token for testing
If you're going to test the integration with the Envia API, you'll need to generate a specific token within the test environment.
- Log in to
shipping-test.envia.com(your test account). - Go to Developers > API Access.
- Click Add to generate a new token.
- Copy the token and use it in your calls to the sandbox endpoints.
ℹ️ Use this token only with the sandbox URLs. If you use it with the production URLs, you'll get an authentication error, and vice versa.
Limitations of the test environment
The sandbox replicates the production environment, but with some important differences:
- The generated guides They aren't real. and they don't offer tracking through shipping carriers.
- Payments and Balance Top-Ups are not processed; the balance in the sandbox is fictitious.
- Some integrations with shipping carriers may behave differently or may not be available in test environments.
- Sandbox data (addresses, packets, history) is separate and is not synchronized with your production account.
Go into production
Once you've validated your flows in the sandbox, the next step is to go live in production.
- Log in to your production account at
shipping.envia.com. - If you need an API token, generate it at Developers > API Access from your production account.
- If you have an API integration, replace the URLs.
- Replace the sandbox token with the production token.
Make sure your production account is verified before generating actual shipping labels. See the article Verify account if you have any pending steps.
FAQ
Can I use my production account for testing? This is not recommended. The guides generated in production are real and result in charges. Always use the sandbox for testing and development.
Is the balance I have in production available in the sandbox? No. The balance, addresses, packages, and history are completely separate between the two environments.
Do I need to verify my account in the sandbox? No. In the test environment, you can operate without going through the identity verification process that applies in production.
Are the shipping carriers available in the sandbox the same as those in production? For the most part, yes, although some package managers may have limited availability or behave differently in the test environment.
Can I access both the sandbox and the production environment at the same time? Yes. They are separate accounts, and you can be logged in to both at the same time using different browsers or tabs.
Is it mandatory to use the sandbox environment? No, but we recommend it to minimize errors before going live in production, especially if you're going to connect an e-commerce store or integrate the API.
Did you find this resource useful?