> 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/jp/backend/backend-api/older/backend-api-version-16.2.8.md).

# Backend API Version 16.2.8

Released on Oct 18, 2021

## Bug Fixes

* KA-4220: GovCloud Email device approval link broken
* KA-4219: GovCloud Change Email Address function broken
* KA-4255: GovCloud Change Master Password email notifications not being sent
* KA-4364: Account Transfer of Read Only direct record shares to transferee get elevated permissions (edit/share) for transfer recipient

## Features and Improvements

* KA-4264: API to convert non-type records to Record Types
* KA-4280: Added Compliance Reports event logs to Advanced Reporting & Alerts module
* KA-4298, KA-4300: Vault Transfer support for Record Types records (in Admin Console)
* KA-4316: Better handling of connection timeouts when setting up the Keeper Automator
* KA-4350: Added support for Devo (SIEM provider)


---

# 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.keeper.io/release-notes/jp/backend/backend-api/older/backend-api-version-16.2.8.md?ask=<question>&goal=<user_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.