Lightspeed · Rate Limits

Lightspeed Pos Rate Limits

The Lightspeed Retail R-Series API enforces a per-account leaky-bucket rate limit. Each request adds a variable cost (X-LS-Api-Request-Cost drips) to a bucket that drains at one drip per second (X-LS-Api-Drip-Rate); the account's bucket size scales with the number of registers on the subscription. The X-LS-Api-Bucket-Level header reports current fill as level/size. Exceeding the bucket returns HTTP 429. The Retail X-Series (Vend) API and Restaurant K-Series API apply their own per-key request throttling and likewise signal back-pressure with 429 plus Retry-After. Limits are per-account / per-API-key rather than per-IP.

Lightspeed Pos Rate Limits is the machine-readable rate-limit profile for Lightspeed on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring leaky_bucket_drips, varies, and requests_per_second.

Limit state is signalled in the bucketLevel, burstLevel, dripRate, and requestCost response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include POS, Retail, Restaurant, Ecommerce, and Rate Limiting.

4 Limits Exhausted: HTTP 429 bucketLevelburstLeveldripRaterequestCost
Method: generated, dated 2026-06-02.
Written by API Evangelist on 2026-06-02 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
POSRetailRestaurantEcommerceRate LimitingQuotasThrottling

Limits

R-Series leaky bucket (per account) account
leaky_bucket_drips
bucket size scales with register count; drains at 1 drip/second
Each request adds X-LS-Api-Request-Cost drips; the bucket leaks one drip per second (X-LS-Api-Drip-Rate). Current fill is reported as X-LS-Api-Bucket-Level (level/size). 429 once full.
R-Series request cost account
varies
per-operation drip cost (read operations cheaper than writes/bulk)
Expensive operations consume more bucket capacity per call.
X-Series (Vend) request throttle key
requests_per_second
see x-series-api.lightspeedhq.com/docs/rate_limiting
Per-API-key throttling; honor 429 and Retry-After.
K-Series (Restaurant) request throttle key
varies
per-client throttling; honor 429
Restaurant K-Series applies per-client back-pressure on the Order & Pay and data endpoints.

Policies

Leaky-bucket pacing
On R-Series, read X-LS-Api-Bucket-Level before issuing bursts; keep level well below size and let the bucket drain at 1 drip/second. Batch or cache reads to lower aggregate request cost.
Backoff strategy
Implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Scope awareness
Limits are bound to the account (R-Series, scaling with registers) or the API key (X-Series, K-Series), not the client IP. Provisioning more registers raises the R-Series ceiling.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/lightspeed-pos-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.