x-lifi-api-key
and are calculated per API key across all endpoints. These limits help prevent abuse and ensure a smooth experience for everyone.
Endpoint Scope | Rate Limit |
---|---|
200 requests per two hours | |
Rest of endpoints | 200 requests per two hours |
Endpoint Scope | Rate Limit |
---|---|
200 requests per minute | |
Rest of endpoints | 200 requests per minute |
🔒 Higher limits may be available for enterprise clients. Please see our Plans page for more details.
429 Too Many Requests
HTTP response. When this occurs:
GET /tokens
, GET /chains
, and static endpointsx-lifi-api-key
with an API key. If you are using the Client SDK, you will set the API when creating a config, and then the SDK will send the header on your behalf with every request. If integrating directly with the API, you’ll need to send this header yourself like so:
x-lifi-api-key
in client-side environments such as browser-based JavaScript or direct Widget integrations. Using the API key on the client side can lead to unauthorized usage or abuse of your key, as it becomes publicly accessible in the browser’s developer tools or network tab.
If you’re using the LI.FI Widget, you do not need to pass an API key. The Widget operates securely without requiring a key in the frontend. For server-side integrations (e.g. SDK or API requests from your backend), always keep your key secret and secure. 🛠️ For advanced usage recommendations and caching strategies, see Performance & Optimization.