Changelog
Back to All
Added

Partner API v3 Release

6 months ago by WeTravel Admin

Release type: Major

Migration required: Yes

Affected APIs: Trips, Payment Links

Backward compatibility: ❌ Breaking

Summary

Partner API v3 introduces a redesigned data model for Trips and Payment Links, removing draft and publish concepts, simplifying endpoint structure, and aligning public APIs with WeTravel's internal systems.

Integrations using Trips or Payment Links should migrate from v2 to v3 to continue using these APIs.

🔴 Breaking changes

General

  • Base URL version changed from /v2 to /v3.
  • Requests are no longer wrapped in { data: { … } }.
  • Several legacy field names were renamed for consistency.
  • Response payloads may include additional (additive) fields.

Trips API

  • Draft trips removed
    Trips are no longer created or managed as drafts.
  • Publish endpoints removed
    Trips are published immediately on create and update(no draft or explicit publish step).
  • Default pagination size reduced
    per_page default changed from 1000 → 25.
  • Filtering parameters changed
    • Removed: exclude_payment_links
    • Added: archived, deactivated, currency, departure_date, recurring, visibility
  • Sub-resources consolidated
    Multiple endpoints (packages, options, discounts, images, etc.) are now represented as nested arrays and objects within the trip payload.
  • Field renames
    Several fields were renamed (for example: trip_id → external_id, group_min → min_people).

Payment Links API

  • Publish behavior removed
    • publish_status and publish_immediately removed
    • Payment links are usable immediately after creation or update
  • Update method changed
    • PUT → PATCH
  • Pricing structure updated
    Pricing fields are now grouped under a unified package object

🟡 Behavioral changes

  • Create and update operations for trips and payment links publish resources immediately.
  • Pagination behavior differs due to lower default page size.

🟢 Unchanged

  • Authentication flow and scopes
  • Access token lifetime (1 hour)
  • Pricing units:
  • Other APIs remain unchanged:
    • Bookings API
    • Transactions API
    • Suppliers API
    • Leads API

Migration guidance

See Migration v2 → v3 for:

  • Endpoint mappings
  • Field-level changes
  • Example requests
  • Testing and validation recommendations

Final note

This changelog is intentionally concise.
All implementation details live in the Migration v2 → v3 guide.