Managing Rate Limits for Retool Embed URLs with Frequent View Changes

External Apps
1

Hi everyone,

I'm integrating Retool Embed into my React app with an Express backend. Since embed URLs are single-use, I generate a new embedUrl each time a user accesses the Retool view (there's a sidebar to navigate across multiple views, where only one is a Retool embedded app). This works fine, but when users frequently switch views, it results in multiple requests to /api/embed-url/external-user.

Considering the API rate limits:

API Rate Limits

  • Up to 300 points in a 60-second window
  • Endpoint costs:
    • Apps, Folders, Users: 2 points
    • Others: 5 or 10 points

I'm concerned about hitting these limits if many users navigate simultaneously.

My questions are:

  1. What is the point cost for the /api/embed-url/external-user endpoint?
  2. How can I handle frequent view changes without exceeding rate limits?
  3. Is there a secure way to reuse or extend the validity of the embedUrl?
  4. Any best practices for caching or session management in this scenario?

Any guidance would be greatly appreciated!

Thank you!

2

Hey @fagiannoni! Thanks for reaching out.

I've been seeing more and more use-cases for embedding Retool, which is exciting. :slightly_smiling_face: I'm pretty confident that this particular endpoint isn't rate-limited in the same way that that the set of public API endpoints are, so you should be good!

I'll confirm that and let you know here. In the meantime, feel free to follow up with any additional questions. :+1:

UPDATE: I can confirm that the endpoint for generating an embed URL is not rate-limited.