> 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.0.8.md).

# Backend API Version 16.0.8

Released on Jun 25, 2021

## Bug Fixes

* KA-4097: Australia data center unable to perform Vault Transfer
* KA-4077: Support RFC7159 "Accept: application/json" and "Accept: application/scim+json"
* KA-4078: Support for Account Recovery of expired free users.
* KA-4055: Support for Account Recovery of SSO users with clients implementing Login V3
* KA-4103: Vault login not properly redirecting the user to the proper datacenter upon clicking on the device approval link.

## Improvements

* KA-3800: Implemented Role Enforcement policies for Record Type creation
* KA-4074: Improved Session Invalidation upon the following events:
  * Changed 2FA
  * Change master password
  * User locked by Enterprise Admin
  * User locked by Keeper Support
  * Device locked by Enterprise Admin
  * Enterprise user deleted
  * User deleted via SCIM
  * Enterprise deleted
  * MSP managed company deleted
  * MSP managed company removed<br>
* KA-4080: In case of downstream SMS 2FA provider failure, Keeper can offer support for email delivery of 2FA codes.


---

# 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/backend/backend-api/older/backend-api-version-16.0.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.
