> For the complete documentation index, see [llms.txt](https://docs.rainbird.ai/rainbird/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbird.ai/rainbird/knowledge-modelling/publishing-your-km/api-management.md).
# API Management
Obtain integration details for your knowledge map and configure access control to your evidence data.
For details on integration, more information can be found in our [Developer Guides](/rainbird/developer-docs/overview.md).
## Integration details
To support integrations into your knowledge map you will need to use the correct URL, KMID and API key for authentication. These can all be obtained in one place. With the knowledge map open, navigate to **Publish** and copy the necessary details.
## Access control
Access to the evidence tree and interaction history data is protected by additional security keys, required by default to provide an enhanced security measure.
These keys will need to be provided for any request for evidence or interaction data.
However, for some scenarios it is necessary to remove this enhanced authentication so the evidence tree, for example, can be opened by anyone that has been shared the link.
To enable link sharing on this data, simply toggle sharing on.
Enabling link sharing for evidence and interaction data
---
# 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://docs.rainbird.ai/rainbird/knowledge-modelling/publishing-your-km/api-management.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.
