Owner filtering for Trips and Payment Links

Change type: added

Release type: Minor

Migration required: No

Affected APIs: Trips, Payment Links

Backward compatibility: Compatible

Summary

Partners can now filter Trips and Payment Links by owner_id and update ownership through the Partner API V3.
This enables partners to organize and manage resources by the user responsible for them without changing existing workflows.

Impact

Who is affected: Partners using the Trips or Payment Links APIs
Breaking change: No
Key risk: None — the new parameter and fields are optional.

Changes

Trips API

🟢 Added

owner_id query parameter to GET /v3/trips for filtering Trips by owner.
Ability to update owner_id using PATCH /v3/trips/:uuid.

Payment Links API

🟢 Added

owner_id query parameter to GET /v3/payment_links for filtering Payment Links by owner
Ability to update owner_id using PATCH /v3/payment_links/:uuid.

Access & Ownership Rules

Updating the owner_id does not automatically grant access to the assigned user. Ownership can only be updated to a team member who already has access to the Trip or Payment Link.

Key points:

Changing owner_id does not modify permissions.
The owner_id can only be updated to a team member who already has access to the resource.
If the current owner loses access to a Trip or Payment Link, the owner_id is automatically reassigned to the organizer_id.
For Trip creation, the requesting user must already have permission to create Trips. When a Trip is created, access is automatically granted according to the existing access rules.

What you need to do

Use the owner_id query parameter when listing Trips or Payment Links if you need owner-based filtering.
Include owner_id in PATCH requests to update the owner of an existing Trip or Payment Link.
Update internal integrations if you plan to use ownership as an organizational label.

Learn more

Final note

These additions make it easier to organize Trips and Payment Links by ownership without impacting existing integrations.