API Rate Limit inconsistency

fbcto · May 13, 2020, 1:25pm

The proper approach seems to be like @jasondark suggested on April 9.

If you, like me, feel that setting up a queue and auto-failover system is a bit too much, I have created this small script that you can plug into your existing code and handle any rate limit errors for you with very little change to your existing code.

The biggest disadvantage with this script is that it has the risk of timing out, if the webflow API is not providing a new pool of requests within the script timeout you have set up.

gist.github.com

https://gist.github.com/ahallora/07977f0b79785a0602872f5fdba881e4

README.md

# Webflow API rate limit workaround
This is a naive work-around to the glitchy rate limiter of the current Webflow API. Any suggestions
to optimizations is much appreciated.

## How to use
It's a wrapper to your existing webflow-api functions, where you define two parameters:
1) a collection ID and
2) the function you want to call

If you have reached the rate limit this wrapper will handle the error and try to reset the rate

This file has been truncated. show original

example.js

import { webflowRateLimiterWorkaround } from "webflowAPI-ratelimit-workaround.js";
/* don't forget to also import and configure webflow-api */

const getCollection = async ({collectionId}) => {
  return await webflowRateLimiterWorkaround({
      collectionId,
      callback: async () =>
          await webflow.items(
              { collectionId },
              {

This file has been truncated. show original

webflowAPI-ratelimit-workaround.js

const sleep = async ms => await new Promise(r => setTimeout(r, ms));


export const webflowRateLimiterWorkaround = async ({ collectionId, callback }) => {
    while (true) {
        const hitIt = async () => {
            const x = await webflow.items(
                { collectionId },
                {
                    limit: 1,

This file has been truncated. show original