Car rental order details – Migrating to v3.2
Learn how to update your integration to support /orders/details/cars in Demand API v3.2. This guide explains breaking changes, new nested structures, and recommended migration practices.
Summary of key impacts
- No changes to request schema.
- Responses remain structurally compatible except for payment timing enum changes.
- No fields were removed, but some enum values were renamed, which requires parser updates.
- No new required fields.
Breaking changes
Breaking changes
These are the only breaking or integration-impacting changes between 3.1 and 3.2 versions.
| Field / Area | v3.1 | v3.2 | Type of Change | Impact |
|---|---|---|---|---|
| products.policies.payment.timing | pay_now, pay_local, | pay_online_now, pay_at_pickup, | Breaking (enum change) | Requires mapping updates. Requests using old mappings may misinterpret payment rules. |
| Description of timing values | Not explicitly aligned with car rental UX wording | Updated to reflect clearer car-rental payment flows | Non-breaking but semantic change | Improves clarity; partners should align front-end wording. |
Quick migration summary
Your existing requests for car order details will continue to work in v3.2 without modification.
The only required change is updating your response parser to use the new payment-timing enum values. All other fields and structures remain unchanged.
| Change | Impact | Notes |
|---|---|---|
Replace pay_now → pay_online_now | High | Update parser, UI labels, and internal mapping. |
Replace pay_local → pay_at_pickup | High | Required to correctly interpret the payment model. |
Keep supporting unknown | Low | No change. |
| Verify any payment-timing decision logic | Medium | Totals and commission flow are unchanged, but timing influences your logic for payment collection. |
| Update unit tests relying on old enums | Medium | Old example payloads will not match v3.2 responses. |
Other services details
Refer to orders/details migration guides for details:
3.2 Orders/details migration
Explore how to migrate to v3.2 and retrieve richer booking details for multiple verticals, including accommodation, filghts, cars, and attractions (in Beta).
3.2 Orders/details/accommodations migration
Explore how to migrate to v3.2 and retrieve richer booking details for accommodation.
What's next
- Review the /orders/details migration guide.
- Check the v3.2 Orders API reference for details in fields.
- Contact your Booking.com technical account manager for migration support.