question

bobbygill avatar image
bobbygill asked bobbygill answered

Hitting Clover API Rate Limit after migrating to Short Lived OAuth Token - 429 Too Many Requests

We are having mobile app where user can place order. In back-end we are using Clover API to create orders on the Clover and Doing Payment.

After migrating to OAuth token as per https://docs.clover.com/docs/legacy-token-migration-flow, now we have started receiving 429 Error frequently.

  {
        "message": "429 Too Many Requests",
        "error": {
            "code": "processing_error",
            "message": "429 Too Many Requests"
        }
    }

I have checked documentation and I believe we might be hitting Rate Limit as per this link: https://docs.clover.com/docs/429-too-many-requests

Here are few questions:

1. Why are we getting this Rate Limit only after migrating to Short lived Token?
2. We were not getting this Rate Limit with Non-Expiring tokens which we were using previously.
3. Is there any possibilities of requesting higher Rate Limit?
4. Is there any other way to get rid of this Rate Limit issue other than using Retry Logic as mentioned Rate Limit documentation?

REST APIe-commerce apiAPI Token
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
bobbygill avatar image
bobbygill answered

Any update here?

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community