> 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/backend-api-17.2.md).

# Backend API 17.2

### Features

* **KA-5992**: KeeperPAM ARAM events
* **KA-5959**: PAM functionality on time-limited access for PAM record types
* **KA-6070**: Role policies to create one-time shares and self-destructing records

### Improvements

* **KA-5700**: Endpoint to detect and correct security score inconsistencies

### Bug Fixes

* **KA-6018**: Accessing one-time shares after expiration should not generate ARAM events
* **KA-6101**: Display root company logo in one-time share inside subnode users
* **KA-6142**: Rotation history showing empty in Admin Console
* **KA-5843**: Not receiving alerts for certain events
* **KA-6280**: Allow data modifications with KSM using apps with over 30k records

Various security fixes from NCC Group and Cybertest pen tests


---

# 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/backend-api-17.2.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.