API and management keys
Choose the right EUrouter key for model requests or organization management, with workspace access, read-only permissions and optional expiration.
Use an API key to call models. Use a management key to automate organization settings and manage API keys without signing in to the dashboard.
API keys use eur_<public-id>.<secret>. Management keys use eur_mgmt_<public-id>.<secret>.
API keys call models and let you inspect their own metadata and requests. Management keys automate administrative operations and can be limited to read-only access or one workspace. The server also checks the creator's current organization role.
The public model and provider catalogs work without a key. Both key types use the same API base URL and Authorization: Bearer header. Management keys cannot call inference endpoints.
| Operation | API key | Management key |
|---|---|---|
| Call models | Yes | No |
| Read the authenticating key's metadata and usage | Yes | Yes |
| Look up request usage and cost | Requests made with that key | The creator's requests within its organization or workspace access |
| Read credit totals and account identity | No | Organization-wide key |
| Manage API keys, routing rules and broadcast destinations | No | Within its organization or workspace access |
| Manage organization settings, members and invitations | No | Organization-wide key |
Full and read-only management keys have the same read access. Only full-access management keys can change resources, run dry runs or send test deliveries.
Create a management key
- Open Settings → Management keys in your organization's dashboard.
- Select Create management key, enter a name and choose the whole organization or one workspace.
- Select Read only for reporting scripts that must not change resources.
- Optionally choose an expiration, then copy the secret. It is shown only once.
Only organization owners and admins can create or manage management keys. A solo account has its own organization, and its user is the owner. A management key stops authorizing management requests if its creator loses the required organization role.
Workspace access and read-only permissions
An organization-wide management key can manage the resources its creator is allowed to manage in that organization. It cannot select another organization.
A workspace-bound management key is restricted to that workspace. It cannot manage other workspaces, organization settings, organization invitations or organization-wide membership.
A read-only management key can read the same resources as a full-access key with the same workspace access. It receives 403 on write requests, dry runs and test deliveries. Access mode and key type are fixed at creation.
Manage API keys through the existing API
Use your management key with /api/v1/keys and /api/v1/keys/{hash}. List and individual-key responses use { "data": ... }. Creation also returns the one-time secret in key.
curl https://api.eurouter.ai/api/v1/keys \
-H "Authorization: Bearer $EUROUTER_MANAGEMENT_KEY"curl https://api.eurouter.ai/api/v1/keys \
-H "Authorization: Bearer $EUROUTER_MANAGEMENT_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Production application","expires_at":"2027-12-31T23:59:59Z"}'Spend limits and usage amounts are in EUR. Management keys have no inference spend limit or default routing rule. A management key can create ordinary API keys. Create additional management keys through Settings → Management keys as an organization owner or admin.
Use GET /api/v1/key to inspect the key used for the request, including its type, expiration and usage.
Expiration and revocation
Both key types accept an optional future UTC expires_at timestamp ending in Z when created. Leave it unset for no expiration. The date cannot be changed afterwards. Create a replacement key before the old key expires.
Last-used timestamps are recorded periodically, so recent activity may take a short time to appear.
An expired key receives 401 with the message API key expired, including when its authentication metadata was cached. Expired keys remain visible in the dashboard until revoked.
Revoke a management key from its Settings tab. Automations using the revoked key stop working. Neither API responses nor the dashboard can recover an existing key's secret.
Management API reference
The API reference includes request and response schemas and the authentication requirements for each endpoint:
| Resources | Reference | Access |
|---|---|---|
| API keys | Keys | Organization or bound workspace |
| Routing rules and dry runs | Routing rules | Organization or bound workspace |
| Broadcast destinations and test deliveries | Broadcast | Organization or bound workspace |
| Workspaces and workspace members | Workspaces | Bound workspace for individual reads, updates and membership; organization-wide key to list, create or delete workspaces |
| Organization profile, credits, members and invitations | Organizations | Organization-wide key |
| Organization policy and Response Healing defaults | Settings | Organization-wide key |
| Credit totals | Credits | Organization-wide key |
| Request log | Logs | Organization-wide key |
| Audit trail | Audit events | Organization-wide key |
| Referral balance and payouts | Referrals | Organization-wide key for the creator's own personal organization |
| Programmatic OAuth authorization codes | OAuth | Creator's personal organization; workspace binding is retained |
Read-only keys cannot write, run routing dry runs or send broadcast test deliveries. Manage management keys and accept organization invitations through the dashboard. Some organization profile and membership operations apply only to team organizations; the endpoint reference describes those requirements.
Use a management key for organization automation and keep your ordinary API key for model requests. See Authentication for bearer headers and Credits for billing.