INNERGY's public API rate limiting just got more accurate. Limits now count usage per endpoint route template, rather than per exact URL.
Previously, requests that differed only by a record ID in the URL, for example a different project or work order ID, were counted separately against the limit.
Now, every call to the same route template, regardless of which ID it targets, shares one rate limit.
Different endpoints are still limited independently of each other, so calling one route doesn't eat into another route's budget.
No action is required for normal usage: typical integrations calling a reasonable number of endpoints at a reasonable pace won't notice any difference.
Note: If your integration cycles through many different record IDs against the same endpoint at high volume, you may hit the rate limit sooner than before. Review your call patterns and add backoff/retry handling if you rely on high-frequency, ID-varying calls to a single endpoint.