LINGLI / Developer documentation
Access Lingli Data APIs with a server-side key
Store Lingli API keys on your server and use the X-API-Key header to call APIs. Learn pre-release key checks and how to respond to a leak.
Lingli Data · Updated 9 October 2026
Lingli’s public integration examples use the X-API-Key header. Create your own key in the console and send the corresponding API requests from your server.
Where to store your key
Store keys in server-side environment variables or a credential management system suited to your deployment. Read the configuration when the application starts and send the key in request headers. Frontend pages should communicate only with your backend; never send real keys to the browser.
The public example uses LINGLI_API_KEY as its environment variable name. This is an application configuration name; API authentication still uses the X-API-Key header.
Pre-release checks
- Check repositories and build artifacts for real keys.
- Check logs, errors, monitoring and screenshots to avoid exposing complete request headers.
- Verify the actual request domain and API path; do not build the API URL from the current webpage’s domain.
- Ensure only services that need to make requests can read the credentials.
Refer to the console and relevant documentation for key status, permissions and API requirements.
Responding to a key leak
Stop sharing files or logs that contain the key and use the console’s available management tools to address the exposed credential. Review potentially affected request records, update your server configuration and verify the new configuration.
Deleting a key from a public repository does not remove historical exposure. If you are unsure which management action to take, contact the service provider first.
Console access and server-side requests
Console login is for account and API management. Server-side requests use your configured API key. Integrations must follow the API documentation rather than reuse a browser login session as public API authentication.