API Best Usage / Rate Limits & Practices
How to use our API and general guidelines
API Usage Best Practices
ResellerRatings does not currently impose fixed API rate limits for accounts that have API access. This may change in the future. We monitor usage and ask that requests remain reasonable and proportionate to your integration’s needs.
All API use is subject to the ResellerRatings API Terms. These best practices supplement those terms.
Rate Limits and Supplemental Fees
ResellerRatings reserves the right to introduce or adjust API rate limits based on usage volume, request frequency, infrastructure demands, or service performance.
Accounts requiring higher-volume access, more frequent requests, or additional capacity may be subject to an API Rate Supplemental Fee, charged in addition to their existing subscription rate. Any applicable fee will reflect the account’s usage and capacity requirements.
We will notify the account of the applicable fee and its effective date before billing begins. Rate limits may be applied immediately where necessary to protect service availability or address excessive or abusive usage.
Schedule Efficient Updates
Choose a refresh schedule appropriate for your use case. Daily pulls are generally sufficient for reporting and marketing workflows. If more frequent updates are needed, hourly pulls are a reasonable starting point.
Avoid continuous polling, and allow each scheduled job to finish before starting another.
Retrieve Changes Incrementally
After your initial import, use fromModified and toModified to retrieve new or updated reviews rather than repeatedly downloading your full review history.
Record the last successfully completed synchronization window. Use a small overlap between runs and deduplicate by review ID to help prevent missed updates.
Confirm how removed or inactive reviews are returned so your local records accurately reflect their current visibility.
Use Efficient Pagination
Use perPage=100 when retrieving larger datasets to reduce the number of requests. Retrieve pages sequentially and avoid large batches of simultaneous requests.
Save your progress so interrupted imports can resume without restarting the entire download.
Handle Errors Gracefully
Set request timeouts and use a limited number of retries with increasing delays between attempts.
Investigate authentication errors and invalid requests before retrying. Repeated failures should trigger an internal alert rather than an endless retry loop.
Protect Credentials and Reuse Tokens
Keep your client secret and access tokens secure in your server-side environment. Do not expose them in browser code, public repositories, or logs.
Reuse valid access tokens until they expire rather than requesting a new token for every API call. Follow the authentication flow’s expiration and renewal instructions.
Keep Content Current and Properly Attributed
Refresh displayed scores, review counts, and review content regularly. Include the required ResellerRatings branding and direct links to the relevant profile or original review.
Ensure that edits, removals, and visibility changes are reflected in your implementation.
Follow Data Retention Requirements
Local storage, caching, and continued use of API content must comply with the ResellerRatings API Terms.
The terms restrict retaining API data beyond 30 days without express permission, subject to the stated exceptions for compliance or internal reporting. Refreshing data does not independently authorize indefinite retention.
Coordinate Larger Workloads
Contact ResellerRatings before unusually large imports, substantial increases in request frequency, or other intensive workloads.
We may contact you to adjust request patterns or restrict usage if activity is excessive, abusive, or affects service performance.