Tres API docs refresh: expanded search options and newly documented endpoints

We have refreshed the Tres Developer Portal to better reflect the current API surface.

This update includes newly documented endpoints, broader search options across many existing *Search methods, and richer field and relationship coverage on several existing entities.

Newly documented endpoints

The following endpoints are now documented in the developer portal:

• AirlineArrivalManifestSearch
• AirlineDepartureManifestSearch
• ClientDocumentAcknowledgementClientProfile
• HotelRoomingListSearch

Expanded search capabilities

Many existing search methods now document additional inherited controls and filters.

Examples include:

• skipLookup
• readOnlyIntent
• priority
• additional range and related-search parameters on selected methods

This affects a broad set of existing *Search endpoints, including examples such as:

• AccountingEntrySearch
• ActivitySearch
• AppUserSearch
• PaymentSearch
• ProfileSearch
• TripSearch

Richer entity documentation

Several existing entity documents now reflect additional fields, relationships, nested tables, deprecations, and enum values.

Examples include:

• AppUser
• ClientProfile
• Trip
• Person
• DocumentTemplate
• Agency
• Branch

What this means for integrators

If you already integrate with the Tres API, this refresh may expose capabilities that were already present in the live API but not fully reflected in the portal.

If you are exploring new integrations, the refreshed docs should make it easier to:

• discover additional search controls
• understand richer response and relationship shapes
• find newly documented endpoint coverage

Next steps

We plan to continue tightening the alignment between the live API and the developer portal so newly available capabilities appear more consistently and with less lag.

We will also follow up on Swagger deep-link support so cross-links from the portal can land more precisely inside the Swagger UI.