# Resolve someone else’s access request

> Source: https://elaichi.ai/docs/api-reference/access-requests/access-request/resolveaccessrequest/

`POST /access-request/{id}/resolve`

Resource: **Access Request** · API: **Access requests**

## Path parameters

- **`id`** _(string, required)_
  Access request id (`areq_…`).

## Request body

- **`decision`** _(string)_
  Allowed: `approved`, `denied`
- **`note`** _(string)_

## Response body

- **`id`** _(string)_
  Access request id (`areq_…`).
- **`requester_user_id`** _(string)_
  User id (`usr_…`) of whoever filed the request.
- **`tool`** _(string)_
  What was asked for: a tool name, or a connector slug when `resource_type` is `"connector"`.
- **`resource_type`** _(string)_
  Allowed: `tool`, `connector`
- **`connector_slug`** _(string,null)_
  On a `"tool"` request, the connector the tool lives on when the request named one — what makes approving it able to lift the restriction on that tool. Always null on a `"connector"` request.
- **`reason`** _(string)_
  What kind of refusal this request is asking to be reconsidered.
  Allowed: `permission`, `restriction`
- **`permission`** _(string,null)_
  Present only when `reason` is `"permission"` — never populated for a `"restriction"`-reason request, on either write or read. That is the disclosure rule: a restriction refusal never names the rule that blocked the caller, so this field must not become a second channel for the same fact.
- **`note`** _(string,null)_
  Optional free text from the requester, ≤ 2000 characters.
- **`status`** _(string)_
  Allowed: `pending`, `approved`, `denied`, `withdrawn`
- **`created_at`** _(string)_
- **`resolved_at`** _(string,null)_
- **`resolved_by_user_id`** _(string,null)_
  User id (`usr_…`) of the admin who resolved it.
- **`resolution_note`** _(string,null)_
- **`updated_at`** _(string)_
- **`requester`** _(object)_
  Resolved member profile. Falls back to `{ id }` alone when the profile row no longer resolves.
  - **`id`** _(string)_
    User id (`usr_…`).
  - **`name`** _(string,null)_
  - **`email`** _(string)_
- **`resolved_by`** _(object,null)_
  Resolved member profile. Falls back to `{ id }` alone when the profile row no longer resolves.
- **`can_resolve`** _(boolean)_
  True while `status` is still `pending` **and** the row is not the caller’s own — the two preconditions `resolve` itself enforces (`409` and `403` respectively).
- **`can_withdraw`** _(boolean)_
  True when the caller is the requester and `status` is still `pending`. Present on this shape as well as on the self view: an admin’s own request sits in their own queue, and withdrawing it is the one verb on that row that is theirs.
- **`will_lift_restriction`** _(boolean)_
  On a pending restriction-reason request approving could act on (a connector request, or a tool request naming its `connector_slug`): whether approving it would actually lift anything. Absent on every other row.
- **`connector_restricted_for_requester`** _(boolean)_
  On the same rows, for a TOOL request only: true when approving lifts nothing because the requester’s WHOLE connector is restricted — one tool cannot be carved out of a connector restricted whole, and an approval never opens the whole connector for a one-tool ask. Their connector access is what an admin would have to grant instead.
- **`connector_label`** _(string)_
  Display name of `connector_slug` on a tool request that names one (falls back to the slug).

## Code examples

### curl

```bash
curl -X POST 'https://api.elaichi.ai/access-request/<id>/resolve' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"decision":"approved","note":"your_note"}'
```

### JavaScript

```javascript
const body = {
  "decision": "approved",
  "note": "your_note"
};

const response = await fetch('https://api.elaichi.ai/access-request/<id>/resolve', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify(body),
});

const data = await response.json();
console.log(data);
```

### Python

```python
import os
import requests

url = "https://api.elaichi.ai/access-request/<id>/resolve"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}
payload = {
    "decision": "approved",
    "note": "your_note"
}

response = requests.post(url, headers=headers, json=payload)
print(response.json())
```