Test and Production Environments for Amadeus Self-Service APIs

When building an application that uses Amadeus Self-Service APIs, it is important to understand the differences between the two environments. As the names suggest, the testing environment is used for developing and testing the application, while the production environment is used for deploying the application to the real world. 

Test Environment 

The Test Environment is used in the initial stage of the application development lifecycle or for trial purposes to explore the potential of Amadeus Self-Service APIs. Below are the most important features of the Test Environment: 

Limitations: Amadeus provides a Test Environment with limited data collections for each Self-Service API. Most of the APIs in the test environment use static cached data. 

No billing: Transactions in the Test Environment are free, and developers do not get billed for their usage, although the number of free calls are limited by the monthly quota. 

Higher rate limits: Self-Service APIs in the test environment are limited to 10 transactions per second.  

Source Code Changes: In the application code, you need to point the base URL for API calls to the Test Environment - test.api.amadeus.com - and use the API Key and API Secret provided specifically for the Test Environment. 

Production Environment 

The Production environment is the final stage of the software development lifecycle where your application is released to the users. Once the application is ready for deployment, you can request a Production Key to access the Production Environment. Below are the most important features of the Production Environment: 

Production Key: To request a Production Key, you need to purchase a subscription and complete a form with your business information, billing address, and app information. After submitting the Production Key request, the application status becomes "pending," and the Amadeus team validates the application. Once the application is validated, the status changes to "live." Production keys are valid for all Self-Service APIs except Flight Create Orders API. 

Flight Create Orders: Applications using Flight Create Orders must meet certain requirements before moving to the Production Environment. 

Billing: Once you exceed the free transaction limit, you will be billed automatically for transactions every month. It is important to know that if you don’t exceed the free transaction limits, you won’t be billed at all. This gives you the benefit of having the production data with no hidden costs or risks of being overcharged. 

Lower rate limits: Self-Service APIs in the production environment are limited to 40 transactions per second. 

Source Code Changes: In the application code, you need to point the base URL for API calls to the Production Environment - api.amadeus.com - and update the API Key and API Secret with the keys provided specifically for the Production Environment

Comparison table 

Conclusion 

In conclusion, the differences between the testing and production environments for Amadeus Self-Service APIs are significant and important to understand. To learn more about the environments and Amadeus Self-Service APIs, refer to our Developer Guides

#amadeusapis #amadeusfordevelopers #travelapi #traveltech #tutorial #developer #testing