Best Practices for Response Queue
- 1 Minute to read
- Print
- DarkLight
Best Practices for Response Queue
- 1 Minute to read
- Print
- DarkLight
Article summary
To effectively use the Response Queue, it is recommended to utilize the REST API over HTTPS for secure data transfer, particularly when handling Personally Identifiable Information (PII). Implement fair usage by configuring the API to allow a maximum of 30 calls per hour for each method, spaced out in 2-minute intervals, to prevent overloading the Mapp Cloud API servers and reduce failure responses. When polling, ensure that only one API call per response type is made at a time, as parallel requests of the same type are not supported. Additionally, it is important to retrieve responses regularly, as the Response Queue service retains events for only 30 days, after which older responses will be overwritten. Following these guidelines will help maintain efficient and secure interactions with the API.
Did you find this summary helpful?
Thank you for your feedback!
Here are some recommendations for effective usage of the Response Queue.
Use REST API in HTTPS
HTTPS ensures that the data is transferred securely, which is especially useful when transferring PII data in those events.
Support Fair Usage
Configure your API to send maximum of 30 calls per hour for each method you are using, e.g. in 2-minute intervals. This ensures that you do not overload Mapp Cloud API servers and minimize occurrences of failure responses.
One API call per type at a time
Ensure that you poll different response types when polling in parallel. Parallel same-type requests are not supported.
Retrieve responses regularly
The Response Queue service stores events for the previous 30 days. After this time, old responses are overwritten.
Was this article helpful?