Production readiness checklist

Verify that your Demand API integration is fully prepared for production. Follow this checklist to ensure proper authentication, environment setup, caching, testing, and monitoring before going live.

Before going live with your Demand API integration, make sure that your implementation meets the following requirements.

Completing this checklist helps ensure stability, compliance, and a smooth experience for travellers.

Authentication and access

✓ Use production credentials.
Confirm that your production X-Affiliate-Id and authentication tokens are correctly configured.

✓ Secure all sensitive data.
Never expose API credentials in client-side code or public repositories.

✓ Handle expired or invalid tokens gracefully.
Implement retry or re-authentication logic according to the Authentication guide.

Environment configuration

✓ Switch endpoints to the production environment.
Update any base URLs or environment variables used for sandbox.

✓ Validate configuration per travel service.
Ensure endpoints for each active travel service (accommodations, cars, or attractions from v3.2) are correctly set up.

✓ Monitor request volume.
Verify that your system can handle expected live traffic and respects Demand API rate limits.

Data management

✓ Implement local caching for static data.
Use the recommended caching approach described in Static data and caching.

✓ Never cache dynamic data.
Do not store prices or availability, as these change frequently.

✓ Ensure proper data refresh logic.
Schedule updates for content and reference data to keep your cache accurate.

Functional testing

✓ Test your integration flow.
Verify your selected integration flow for each supported travel service.

✓ Validate error handling.
Confirm that your integration correctly manages expected errors (for example, 400, 403, or 409) as described in Error handling.

✓ Check edge cases.
Simulate cases such as unavailable inventory, invalid payment methods, or expired sessions.

Payments and orders

✓ Confirm payment flows.
Test payment method handling and timing using /orders/preview and /orders/create.

✓ Verify order management.
Make sure your integration can retrieve, modify, and cancel orders through /orders/details/*, /orders/modify, and /orders/cancel.

Monitoring and maintenance

✓ Implement logging and alerting.
Capture API errors, response times, and other operational metrics for early issue detection.

✓ Track API usage.
Regularly review your usage reports to identify anomalies or rate limit issues.

✓ Stay up to date.
Monitor the Changelog for updates, deprecations, and new features.