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

# Backend API Version 16.0.6

## Bug Fixes and Improvements

* KA-4012, KA-3596, KA-4015:\
  Resolved several Sharing and Emergency Access related API calls to eliminate all possible enumeration attack vectors on Login V3. Also resolved confusing error messages and popups within the application when handling the sharing handshakes between users.\
  \
  Note that in order to share records between users, a sharing relationship must first exist and be established. In the case of Enterprise accounts, a sharing relationship between users already exists. A share relationship must be established manually for all consumer users and Enterprise-to-consumer accounts, or Enterprise users between different tenants.<br>
* KA-4004, KA-4006, KA-4023: Added additional push notifications and auto-syncing to the Admin Console for MSP tenants to trigger instant updates when MC license changes occur, and for Vault Transfer actions.<br>
* KA-4052: Resolved issue where linked Family Plans are not getting enough family member licenses added.


---

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