Sandbox Environment

Online interface

The Sandbox web interface is available at https://sandbox.avinode.com. Use it to create the test data you need (RFQs, quotes, empty legs, etc.) and to view data created through the API.

User accounts

Sandbox user accounts are created for your company when your Sandbox access is set up. We need one valid email address per user, as this is where password reset emails are sent (see Weekly reset).

Shared environment

The Sandbox is shared by Avinode and Schedaero customers and partners who are developing and testing their software. Each company has its own company account, user accounts, aircraft and API connections. However, because Avinode and Schedaero are collaborative platforms, anything you publish (e.g. empty legs, Tripboard posts) or send (e.g. RFQs) may be visible to other developers using the Sandbox.

Weekly reset

The Sandbox is rebuilt with a fresh database at least once a week, usually on Mondays between 06:00 and 08:00 UTC. When this happens:

• Any data created or changed during testing is deleted
• API credentials are reset

API credentials

After each reset, you'll need to generate new tokens for your Sandbox API connection and update them in your integration before it can call the Sandbox API again. If your Sandbox calls start failing with authentication errors after a Monday reset, this is the first thing to check.

To generate new tokens:

1. Log in at https://sandbox.avinode.com.
2. Go to Company -> APIs and select your API connection.
3. In the Authentication Tokens section, click New Token.
4. Select Sandbox API as the token type and click Save.
5. Copy the API Token and Authentication Token and store them securely. Tokens are only displayed once.

Your Sandbox user needs the Company APIs and Technical Staff permissions to access Company -> APIs.

For more detail, see Retrieving API Tokens for Integrations in Avinode. That article describes the production environment, but the steps are the same in the Sandbox.

Downtime

We aim to keep the Sandbox available at all times, but it's occasionally taken down for short periods for maintenance or deployments. If the Sandbox is unavailable for more than an hour, please contact us.

Non-disclosure

Data in the Sandbox (e.g. company names, aircraft information) must not be extracted or disclosed to any third party. This is covered by your API agreement.

Application life cycle

You'll keep access to the Sandbox for as long as your application has access to the production environment. Whenever you update your application, use the Sandbox to verify that it still works as expected.

Any instance of your application built or deployed for development or testing must be prevented from calling the production API and from consuming webhook notifications sent by the production API.