> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/backend/backend-api/older/backend-api-version-16.1.0.md).

# Backend API Version 16.1.0

This backend release provides support for the following major capabilities:

* Keeper Secrets Manager\
  \
  Provides your DevOps, IT Security and software development teams with a fully cloud-based, Zero-Knowledge platform for managing all of your infrastructure secrets such as API keys, Database passwords, access keys, certificates and any type of confidential data.\
  \
  [https://docs.keeper.io/secrets-manager/](https://docs.keeper.io/keeperpam)<br>
* GovCloud Support\
  \
  Keeper is going live with AWS GovCloud in the US data center to support FedRAMP compliant environments. AWS GovCloud is designed to host sensitive data, regulated workloads, and address the most stringent U.S. government security and compliance requirements.\
  \
  To discuss GovCloud and FedRAMP compliance, please email <govsales@keepersecurity.com>.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/backend/backend-api/older/backend-api-version-16.1.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.