List support access granted to your own account's notices
const url = 'https://api.katara.com/katara/v1/account/support-access';const options = {method: 'GET', headers: {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 GET \ --url https://api.katara.com/katara/v1/account/support-access \ --header 'Authorization: Bearer <token>'A signed-in person only. Katara support may be given access to resend an account’s notices that never arrived; this lists every such grant on the caller’s account, newest first, including the expired and the revoked.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Successful request
Support access granted to this environment, newest first.
object
Support access to a person’s own account notices. Only resending notices that never arrived is ever granted on an account.
Example
{ "data": [ { "purpose": "resend_notification" } ]}Account_changed: reload and review with the signed-in account.
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" }}