Withdraw an access request

POST /access-request/{id}/withdraw

Withdraws an access request. Only the request’s own requester may withdraw it, and only while it is still `pending`. No body, and no permission beyond membership. Someone else’s request id is `404`; a request that already left `pending` is `409`.

Path Parameters

idstring

required·

Access request id (areq_…).

Response Body

can_withdrawboolean

True when the caller is the requester and status is still pending.

connector_labelstring

Display name of connector_slug (or, on a "connector" request, of tool itself), falling back to the slug. Present on every view: the requester reads it in the self view exactly as an admin does in the queue.

connector_logostring,null

The connector’s logo for the slug connector_label names. null when the catalog has no logo for the slug; present under the same conditions as connector_label.

connector_slugstring,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.

created_atstring · date-time

idstring

Access request id (areq_…).

notestring,null

Optional free text from the requester, ≤ 2000 characters.

permissionstring,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.

reasonstring

What kind of refusal this request is asking to be reconsidered.

Possible values:

permissionrestriction

requester_user_idstring

User id (usr_…) of whoever filed the request.

resolution_notestring,null

resolved_atstring,null · date-time

resolved_by_user_idstring,null

User id (usr_…) of the admin who resolved it.

resource_typestring

Possible values:

toolconnector

restriction_liftedboolean,null

What an approval did to the requester’s access, on every view: true when it wrote a grant, false when the request was approved and nothing was lifted (a resolution: "policy" approval, access that was already open, or a shape no grant can open), null when the question does not apply (not approved, a permission request, a tool request with no connector_slug). It never says why; the connector’s own restricted, restricted_by and restricted_inherited_from do, within what the caller may be told. An older approval may read false for access it did give, so read the connector’s restricted for the live answer. It is the outcome at resolve time: a later revoke, expiry or replacement does not change it.

statusstring

Possible values:

pendingapproveddeniedwithdrawn

toolstring

What was asked for: a tool name, or a connector slug when resource_type is "connector".

updated_atstring · date-time

curl -X POST 'https://api.elaichi.ai/access-request/<id>/withdraw' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'

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

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

import os
import requests

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

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