> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests.md).

# Requests

Endpoints for listing access requests and creating grant, change permission and remove access requests.

The Requests endpoints allow you to create and track access change requests in Cakewalk: the grant, change and remove access actions that flow through approval workflows before they are applied. These endpoints enable programmatic submission and monitoring of access requests.

These endpoints are useful for:

* Listing and filtering access requests by status, type, or last-updated time
* Submitting grant, change or remove access requests via automation
* Embedding Cakewalk access request flows into external tools or workflows

***

### 📘 Requests Endpoints

<table><thead><tr><th width="287.6328125">Endpoint</th><th width="114.953125">Method</th><th width="102.8671875">Version<select><option value="Rq1VerSelV1x" label="v1" color="blue"></option></select></th><th>Description</th></tr></thead><tbody><tr><td><a href="https://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests/get-requests.md">/{version}/Requests</a></td><td>GET</td><td><span data-option="Rq1VerSelV1x">v1</span></td><td>Returns a paginated list of requests, optionally filtered by status, type, and last-updated time.</td></tr><tr><td><a href="https://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests/post-requests-grantaccess.md">/{version}/Requests/GrantAccess</a></td><td>POST</td><td><span data-option="Rq1VerSelV1x">v1</span></td><td>Creates a grant access request for a user or group.</td></tr><tr><td><a href="https://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests/post-requests-changepermission.md">/{version}/Requests/ChangePermission</a></td><td>POST</td><td><span data-option="Rq1VerSelV1x">v1</span></td><td>Creates a request to change a user's existing permission level.</td></tr><tr><td><a href="https://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests/post-requests-removeaccess.md">/{version}/Requests/RemoveAccess</a></td><td>POST</td><td><span data-option="Rq1VerSelV1x">v1</span></td><td>Creates a request to revoke a user's or group's access.</td></tr></tbody></table>


---

# 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://www.cakewalk.security/docs/human-access/open-api-and-mcp/api-reference/requests.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.
