Summary

This Beta release includes one enhancement to company and travel agent note management via the API. Partners are encouraged to validate this change in Beta and report any issues via standard support channels.

New Features

Company & Travel Agent Notes — All Properties Support

The API now supports creating and updating notes scoped to All Properties for both company and travel agent records, by passing propertyId: 0 in POST and PUT requests. This aligns API behaviour with what is already possible in the RMS UI.

Previously, propertyId: 0 was rejected by the API, requiring notes to be managed on a per-property basis only.

Additionally, validation has been added to PUT requests to ensure the propertyId in the request matches the existing note's scope. Attempting to update an All Properties note with a specific property ID (or vice versa) will return a 400 error.

Endpoints affected:

• POST /companies/{id}/notes — SwaggerHub ↗
• PUT /companies/{id}/notes/{noteId} — SwaggerHub ↗
• POST /travelAgents/{id}/notes — SwaggerHub ↗
• PUT /travelAgents/{id}/notes/{noteId} — SwaggerHub ↗

Note: Using propertyId: 0 creates a note that applies across all properties the token has access to. API users should be intentional when using this scope — if your integration does not have access to all properties, use property-specific notes instead.

Notes

• Release Date: March 25, 2026  Beta only
• Dependencies: None
• There is no impact to Live environments.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests