Authentication
Learn how to authenticate with the Linkt API
The Linkt API uses API key authentication. All requests must include a valid API key in the request headers.
Getting Your API Key
- Log in to your Linkt Dashboard
- Navigate to Settings > API Keys
- Click Create API Key
- Give your key a descriptive name (e.g., "Production API Key")
- Copy and securely store your API key
Store Your Key Securely
Your API key is only displayed once when created. Store it securely in a password manager or secrets vault. If you lose your key, you'll need to generate a new one.
Using Your API Key
Include your API key in the x-api-key header with every request:
Code Examples
Python
JavaScript / TypeScript
cURL
Security Best Practices
Environment Variables
Never hardcode API keys in your source code. Use environment variables:
Server-Side Only
API keys should only be used in server-side code. Never expose your API key in:
- Client-side JavaScript
- Mobile app source code
- Public repositories
- Browser developer tools
Key Rotation
Periodically rotate your API keys for enhanced security:
- Create a new API key in the dashboard
- Update your application to use the new key
- Verify the new key works correctly
- Delete the old API key
Rate Limits
The Linkt API implements rate limiting to ensure fair usage.
| Plan | Requests per Minute | Requests per Day |
|---|---|---|
| Free | 60 | 1,000 |
| Pro | 300 | 10,000 |
| Enterprise | Custom | Custom |
Rate Limit Headers
Responses include headers indicating your rate limit status:
Handling Rate Limits
When you exceed the rate limit, the API returns a 429 Too Many Requests response:
Implement exponential backoff:
Authentication Errors
| Status Code | Error | Description |
|---|---|---|
401 | unauthorized | Missing or invalid API key |
403 | forbidden | API key lacks permissions |
429 | rate_limit_exceeded | Too many requests |
Organization Scope
API keys are scoped to your organization. All resources created with an API key are automatically associated with your organization.
- ICPs, Sheets, Tasks, and Runs are organization-scoped
- Team members with API access can view and manage shared resources
- API keys do not provide cross-organization access
Next Steps
- Quickstart Guide - Create your first workflow
- API Reference - Explore all endpoints
- Core Concepts - Understand the data model