We have implemented concurrency limits on our API

What’s changed?

We have implemented a concurrency limit on outbound payments submitted from the same bank account and a concurrency limit across our whole API. A concurrency limit is a limit on the number of in-flight requests at any time.

1. Outbound payments submitted from the same bank account will have a concurrency limit of 3 requests.

2. All other requests made to our API will have a concurrency limit of 50.

You’ll be able to send another request, once you receive a response to any of your active requests.

When the limit is exceeded the API will respond with a HTTP code 429 - Too Many Requests.

Why have we done it?

These limits will continue to ensure our API is reliable and able to respond to your requests in a timely manner.

How will this affect existing integrations?

You will need to consider these limit changes as part of your implementation ensuring you are tracking active requests, or designing your integration so that requests to our API are performed via a finite pool of threads or workers.

You will also need to handle 429 responses appropriately, using a backoff and retrying the request.

Thanks for reading! You'll be hearing from us again soon.

In the meantime, you can start testing our products right away when you sign up for our sandbox.

If you need support, feel free to reach out through our in-app chat or send a message to product@griffin.com.

We’re always working to improve our products and enhance your experience. Stay tuned for more updates!

Check out our docs

Join our developer Slack community

Experiment with Postman

Follow us on LinkedIn