RMS Product Updates logo
Back to Homepage Subscribe to Updates

Product Updates

Check out the latest features, improvements, and product updates from RMS

Labels

  • All Posts
  • Announcement
  • New Feature
  • Improvement
  • New Channel
  • New Integration
  • Fix
  • BETA
  • Release Candidate
  • Live
  • RMS Pay
  • RMS Booking Engine
  • Partners
  • Rest API

Jump to Month

  • February 2026
  • January 2026
  • November 2025
  • October 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
Powered️ byAnnounceKit

Create yours, for free!

AnnouncementImprovementBETALiveRest API
yesterday

Upcoming API Rate Limit Changes – Action Required

Important Notice: API Rate Limit Updates

We’re introducing new global rate limits for a set of Group Allotment and reference data REST API endpoints (including Companies and Travel Agents).

These endpoints return low‑change data and are intended to be used with caching and webhooks, rather than continuous polling. The changes below are designed to improve platform stability and ensure consistent performance for all partners.


Why this change is being made

We’ve observed sustained high‑volume polling on several Group Allotment endpoints that return low‑change data. In most cases, these resources are expected to be:

  • Cached after initial retrieval
  • Refreshed only when changes occur via webhook notifications

Continuous polling creates unnecessary load and can impact overall platform performance.


What’s changing (Effective Date: February 23, 2026)

The following endpoints will be limited to 60 requests per minute:

  • GET /groupAllotments
  • GET /groupAllotments/{id}
  • GET /groupAllotments/{id}/allotments
  • GET /groupAllotments/{id}/companies
  • GET /groupAllotments/{id}/travelAgents
  • GET /companies
  • GET /travelAgents

Webhooks (recommended approach)

Webhooks should be used as the primary mechanism for detecting changes:

Group Allotments

  • Events: create, update, delete
  • Payload includes groupAllotmentId, which can be used to re‑query the specific resource if needed

Agents

  • Events: create, update
  • Payload includes agentId for retrieving updated agent details

Using webhooks avoids unnecessary polling and ensures updates are processed only when changes occur.

Webhook schema:
Webhooks


What you need to do

  • Cache responses from the affected endpoints
  • Use webhooks to detect changes
  • Re‑query only the affected resource when a webhook event is received
  • Avoid continuous polling
  • Ensure any manual refreshes stay within the new rate limits

Enforcement

  • Rate limits are applied globally
  • Sustained traffic above the limits may be throttled or blocked

Need help?

If you have questions or would like assistance reviewing your implementation, please contact API Support:
Partner & API Support


Avatar of authorRaul Lopez