Rate Limiting

In order to protect our servers from inadvertent service overuse or intentional attack, and to fairly distribute services to all our customers, we have implemented a rate limiting algorithm. When fully deployed, this new algorithm will cause services to either succeed with new warnings or fail with new errors when services are consumed at too high a rate. Programs that consume Projector services should be enhanced to handle rate limiting errors so that they can continue functioning properly. For more information please visit: Projector Rate Limiting Behavior.

Request

The service request contains:

Name	Data Type	Required?	Default Value	Discussion
MinTimeoffDate	date	no		Export is limited to cards no earlier than this date.
MaxTimeoffDate	date	no		Export is limited to cards no later than this date.
ApprovedMinTimestamp	dateTime	no		Export is limited to cards approved on or after this time. To avoid skipping or duplicating cards set this to the last ApprovedTimestamp from the previous result set.
ApprovedIdsAfter	int	no	0	Export is limited to cards with a ReferenceSystemId greater than this. Note that Projector assigns a ReferenceSystemId that is greater than any previously assigned value. To avoid skipping or duplicating cards set this to the last ReferenceSystemId from the previous result set.
MaxRowsToReturn	int	no	1000	The maximum number of cards to be exported. Values greater than 1000 may fail due to system-enforced transaction time limits.
OnlyCountRows	boolean	no	false	If true, then only the RowCount is returned.

Response

For each card in the result set the following data is returned:

Name	Data Type	Discussion
ApprovedTimestamp	dateTime	Time at which the card was approved.
ReferenceSystemId	int	Unique integer identifying the card.
TimeoffReason	string
ResourceReferenceSystemId	string	Unique code identifying the resource.
TimeoffDate	date	Date for which the time was reported.
TimeoffMinutes	int	The number of timeoff minutes.

Browser not supported