> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2024/2024-01-23-ce-separate-api-keys.md).
# 2024-01-23: CE - Separate API Keys in Developer Portal
### Overview
As a customer, you can define separate API keys for each service to have more precise control over API access. This functionality contributes to creating a safer environment by enabling better access management, meeting both the needs of customers and the desired security measures.\
Please see the details within the What’s New table.
### New features
| Features | Benefits |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Manage Scope per service | - Access control: Individual API keys allow precise control over which services or users are authorized to access the API. Each service has its unique key, ensuring access authorizations are more granular.
- Misuse limitation: If a key is compromised or misused, access can be disabled for that specific key without affecting the others.
- Error isolation: If any problems or errors arise, it is simpler to identify the service or user that is impacted.
|
### Fixes and Improvements
None as these are new services.
### Known Problems
No known problems at time of release.
### Documentation and links
User Guide - [Manage API Keys](/user-guides/getting-started/developer-portal/manage-apikeys.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developer.emporix.io/release-notes/archive/2024/2024-01-23-ce-separate-api-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.