Introspect endpoint always returns 60 — need reliable way to fetch true per-site limits (Assets API scaling)

Developers Developer APIs
1

Hello,
We’re building a tool that works with the Assets API (bulk saving alt text in Designer API - Set Alt Text | Webflow Developer Documentation). Everything is working great today — the only blocker for our new update is handling rate limits correctly so we can scale bulk saves efficiently.

The issue:

  • The https://api.webflow.com/v2/token/introspect endpoint always returns ratelimit: 60.

  • This doesn’t reflect actual site limits. From support/docs we know:

    • Starter/Basic = 60 RPM

    • CMS/Ecommerce/Business = 120 RPM

    • Enterprise = custom

    • Publish endpoint = 1 RPM (special case)

Without a way to get the true per-site limit, the only safe option is to throttle all sites to 60 (slowing down higher-tier users unnecessarily) or risk hitting 429s.

Questions:

  1. Is there currently any way (headers, alt endpoint, lookup) to programmatically fetch the actual per-site rate limit?

  2. If not, is there a plan for introspect (or another API method) to return accurate values?

This isn’t blocking existing functionality — but it is blocking us from scaling this update responsibly and giving higher-tier sites the performance they should get.

Thanks!

1 Like
2

Hi @vishal_chiniwar - we’ll take a look into why the introspect endpoint would only return 60. Is the token you’re testing with tied to a single site that has CMS/Ecom/Business that you know would have a higher rate limit? Or potentially other sites/a whole workspace?

A more accurate strategy would be looking at the headers of an API response for something like the X-RateLimit-Remaining which should reflect the remaining amount of calls in that minute window.

1 Like