localis

Type a CPT/HCPCS code, a place, a service in plain words, or a whole claim line like 90837 LCSW 94110.

Try

2 min read Updated August 8, 2026

Rate limiting an API you bill by the code, not the request

Our /v1 API has three shapes: a single-code rate lookup, a bulk lookup (up to a few hundred codes in one call), and a claim-check endpoint that prices a whole line-item list at once. If a daily rate limit only counted requests, those three would look identical to it — and that isn't really a limit at all. A caller who hits a per-request cap on single lookups could keep going indefinitely by switching to bulk calls of 300 codes each, doing hundreds of times the work per "request" the limit was counting.

The limit scales with the work

Localis's daily quota is scaled to the work each call actually does, not to the number of calls. A single-code lookup counts as one unit against your quota. A bulk call counts one unit per code, and a claim-check call counts one unit per line item. A 300-code bulk call and 300 single-code calls cost the same against your daily quota — bulk is a convenience, not a way around the limit.

That also means a request that gets rejected for being over the limit doesn't cost you anything. If you're right at your quota, checking whether a call fits is free; only calls that actually go through draw down your budget.

Your account's limit doesn't change based on how many API keys you've issued. A quota is tied to your account, not to any one key, so splitting traffic across a staging key and a production key doesn't give you a bigger combined limit.

Staying up during a backend hiccup

The rate limiter itself depends on infrastructure that, like anything, can have a brief hiccup — a restart, a failover, a few seconds of latency. When that happens, Localis is designed to let requests through unthrottled for that short window rather than reject every API call until the dependency recovers. A few seconds of relaxed throttling during a rare blip is a far better outcome than the API going down.

What this means for you

If your integration mixes single lookups, bulk calls, and claim checks, you're working against one quota that reflects what you actually asked the API to do — not one that penalizes you for using the endpoints built to save you round trips. See the API documentation for current limits and endpoint shapes.

← All posts