End a support access grant on your account
const url = 'https://api.katara.com/katara/v1/account/support-access/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/revoke';const options = { method: 'POST', headers: {'X-Katara-CSRF': '1', Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.katara.com/katara/v1/account/support-access/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/revoke \ --header 'Authorization: Bearer <token>' \ --header 'X-Katara-CSRF: 1'A signed-in person only. Revoking twice is revoking once. Granting happens outside the product; ending an access belongs to the account whose notices it reaches.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Browser cookie mutations require value 1 and an allowed Origin. Session bearer clients may omit this header.
Responses
Section titled “Responses”Successful request
Support access to a person’s own account notices. Only resending notices that never arrived is ever granted on an account.
object
Example
{ "purpose": "resend_notification"}default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}