When creating an API solution you will get access to the Sandbox. This environment should be used during development and testing. Making development or testing-related calls to the live environment is strictly forbidden.
The online interface for the Sandbox server can be accessed by browsing to https://sandbox.avinode.com. The online interface can be used to create data needed for testing (RFQs, quotes, empty legs, etc.) and also for viewing data created through the API.
Sandbox user accounts for the online interface will be added to your sandbox account when it's set up. You will need to provide one valid email address per user.
The Sandbox environment can at any time be used by several Avinode and Schedaero customers and partners that are developing and testing their software. Each company or partner has its own company accounts, user accounts, aircraft, and API connections. However, due to the collaborative nature of Avinode and Schedaero, publishing information (e.g. empty legs, Tripboard posts, etc.) and sending messages (e.g. RFQs) will potentially make them visible to other developers using the Sandbox.
The sandbox server is rebuilt with a fresh database at least once a week. This means that data changed or created during tests will be deleted. Usually the weekly data reset occurs between 6-8 AM UTC on Mondays.
Weekly password reset
Because of the weekly data reset in sandbox (including user accounts and passwords) each user in sandbox has to request a password reset email at login the first time every week. The password reset email will be sent out to the email address provided when setting up the user account. It's OK to set the same password every week.
We strive to keep the Sandbox available at all times but occasionally we need to take it down for short periods to do maintenance, deploy new code, etc. If you experience longer down-times than one hour, please contact us and we will try to fix the problem as soon as possible.
Any data that exist in the Sandbox server (e.g. company names, aircraft information etc.) may not be extracted or disclosed to any third party. This is regulated in the API contracts.
Application Life Cycle
As long as your application has access to the live environment, you will also have access to the Sandbox environment. When you update your application, you should use this to verify that your application still functions properly.
Any instance of the application built or deployed for development or testing purposes should be restricted from calling the live API servers and also from consuming webhook notifications delivered by the live API servers.
Updated 6 months ago