Authentication
How to authenticate with the Inkeep Analytics API
Authentication
All Analytics API endpoints require authentication using an API key provided in the request headers.
Authentication Header
Include your API key in the Authorization
header of each request using Bearer token authentication:
API Key Generation
Get an API key
- Log in to the Inkeep Dashboard
- Navigate to the Projects section and select your project
- Open the Integrations tab
- Click Create Integration and choose API from the options
- Enter a Name for your new API integration.
- Click on Create
- A generated API key will appear that you can use to authenticate API requests.
API Key Access Levels
API keys have different access levels depending on the integration type:
- API Integration Keys: Provide both read and write access to the Analytics API
- Other Integration Keys: Some integration types may have restricted access (write-only access)
Always use an API Integration key for full access to all Analytics API functionalities.
Integration Types and Access Levels
Integration Type | Access Level | Description |
---|---|---|
API (Server-side) | Full Access | Can both send and retrieve data from all Analytics API endpoints |
Web (Docs, Website) | Write Only | Can only send data, cannot retrieve analytics |
Slack | Write Only | Limited to sending conversation data |
Support Copilot | Write Only | Can only log support interactions |
Discord | Write Only | Limited to logging community conversations |
MCP | Write Only | Limited to sending platform-specific data |
Project Scoping
All API keys are scoped to the specific project in which they were created. An API key cannot be used to access data from other projects. This ensures proper security isolation between different projects in your Inkeep account.
Security Best Practices
When using the API key in your applications:
- Never expose the API key in client-side code
- Use environment variables to store the key securely
Rate Limiting
The API implements rate limiting to prevent abuse. If you exceed the rate limits, you may receive a 429 Too Many Requests
response. Implementation details vary based on your usage plan.
For more information on API access or issues with authentication, contact Inkeep support.