I’m curious if there’s a limit to how many API resources can be created for a single dashboard.
For context, we’ve run into a limitation with one of our dashboards that would require creating many unique API calls – each one responsible for saving a specific field in one of our database tables.
For example, this could potentially mean creating around 120 API resources tied to the same dashboard.
Is there a limit to the number of resources we can add to a single dashboard, or are they effectively unlimited?
Hi @alessyl ,
I’m not aware of a hard limit on the number of API resources you can create for a dashboard — in practice they’re pretty flexible.
That said, creating ~120 API calls just to save individual fields might be a sign there’s an opportunity to simplify the pattern a bit.
A couple approaches that often work well:
- Send one payload instead of one call per field – pass a JSON object and update multiple fields in one request.
- Use a workflow or backend endpoint that the dashboard calls once, and that workflow handles the multiple updates or API calls behind the scenes.
- Use one REST resource with different endpoints rather than creating a separate resource for each call.
So while there isn’t really a strict limit, consolidating the update logic can often make the dashboard simpler and easier to maintain.
1 Like