The Tres Developer Portal now reflects the API documentation shipped with AppServer 1.7.5.5.

This refresh adds a new trip remarks reference, documents profile-to-PNR relationships, expands trip and search data, and makes several deprecations and corrected data types visible to integrators.

Trip remarks and trip data

TripRemarks is now documented as a dedicated API resource, including the view options that control where each remark appears.

The Trip and TripSearch references now cover additional remarks, warning, fare, ticket, itinerary, and profile-related data. Existing trip remark fields are also identified as deprecated where the dedicated remarks tables should be used instead.

Profile PNR entries

The ClientProfile and Person references now document their PNR-entry relationships, including GDS type, description, move behavior, and value.

ClientProfileMergeToPnr also documents the client and traveler PNR-entry data used during a merge.

Search and schema refinements

This update includes additional filters and fields across several references, including:

  • application-setting name searches
  • trip-import record-locator searches
  • supplier duplicate detection
  • traveler-portal visibility and address-print options
  • corrected DateTimeOffset types for completed action-item dates

The refreshed docs also call out deprecations such as the stored GeneralLedgerAccount balance and legacy payment-card token fields, helping integrators move toward their supported replacements.

What integrators should do

Review the refreshed schemas if your integration reads trip, profile, payment, or accounting data. New fields can expand available output, while newly documented deprecations identify fields that should not be the basis of new integration work.