Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
 

...

Why am I receiving a 'Throttle limit reached, please try again later...' message?

You have breached the throttle limit that is placed on all our pmsXchange V2 connections. There are 3 breaches that will generate this response:

...

Note
SOAP Fault - High Server Load


What are the throttle parameters I need to work within?

Request per minute throttle = 40 

Messages per request (message size) = 500 messages

Concurrent requests Limit = 3

NOTE: These throttle parameters are what you'll have when you go through our certification process, and will be the initial throttle parameters you initially have in production. These parameters can be tweaked in consultation with our Application Operations team as the number of hotels you have grows. You'll be given contact details for the Application Operations team once you are certified and live in production.


Do I need to send 'Delta' updates to pmsXchange when a change is made in my pmsXchange connected integration?

Yes, it is extremely important that you only push 'Delta' changes to pmsXchange. Full refreshes are only allowable a maximum of once per day. Many throttling breaches are to due large requests being sent, even though only small amounts of data have changed in the upstream integration.

...

With more and more partners coming on board everyday, we need to actively throttle to maintain performance for all partners using pmsXchange (especially if you are generating larger than normal size/frequency requests). Throttling has always been something we've always had as part of the pmsXchange spec, and we're now actively looking to apply known throttle parameters to all partners.

...