LastPass · Rate Limits

Lastpass Rate Limits

LastPass throttles abusive Enterprise API traffic and protects authentication endpoints with adaptive rate limiting (failed-login backoff, captcha, account lockout). Per-second numeric ceilings for the Enterprise API are not exhaustively published; LastPass guidance is to batch user-management commands (batchadd, batchchange) instead of single-user calls and to use the SCIM endpoint for ongoing directory sync. Reconciliation against a published numeric ceiling pending - confirm with LastPass support for high-volume integrations.

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

It captures 3 rate-limit definitions, measuring requests and failed_logins.

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 4 backoff/retry policies defined and response codes documented for throttled and unauthorized.

Tagged areas include Security, Password Manager, Vault, Identity, and Enterprise.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-08.
Written by API Evangelist on 2026-05-08 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
SecurityPassword ManagerVaultIdentityEnterpriseRate LimitingThrottling

Limits

Enterprise API Throttle customer
requests · minute
dynamic
Dynamic throttle applied per enterprise customer (cid). Numeric ceiling not published; sustained excessive request volume can trigger temporary block.
Authentication Endpoint Throttle account
failed_logins
adaptive
Failed authentication is met with progressive backoff, captcha, and eventual lockout. Applies to user logins, not the Enterprise API itself.
SCIM Provisioning tenant
requests · minute
dynamic
The SCIM endpoint applies its own dynamic throttle suited to directory-sync patterns from Okta, Entra ID, and Google Workspace.

Policies

429 Throttling
The Enterprise API returns 429 / generic error on excessive throughput. Clients should back off before retrying.
Batch Operations
Use batchadd, batchchange, and other batch commands rather than per-user calls to reduce request volume.
Prefer SCIM For Directory Sync
Use the SCIM 2.0 endpoint for ongoing directory provisioning; it is built for sustained sync patterns and integrates natively with major identity providers.
Backoff Strategy
Implement exponential backoff with jitter on 429/5xx responses; cache reporting results where the underlying data is not changing rapidly.

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/lastpass-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.