Accept the exact reviewed invitation
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/invitations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/accept';const options = { method: 'POST', headers: { 'Idempotency-Key': 'example', 'X-Katara-CSRF': '1', Authorization: 'Bearer <token>', 'Content-Type': 'application/json' }, body: '{"token":"example","expected_digest":"example","expected_version":1}'};
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/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/invitations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/accept \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: example' \ --header 'X-Katara-CSRF: 1' \ --data '{ "token": "example", "expected_digest": "example", "expected_version": 1 }'Session only. The intended verified, active and unbanned recipient (for an email invitation, the signed-in account whose confirmed email address matches it) must present the one-use token in JSON and the exact review digest and invitation version. Current inviter account and organization member-administration authority are rechecked under the organization lock. Changed review returns 409; unavailable, expired, revoked or consumed invitation returns 403, and an email invitation opened by another account returns 403 invitation_address_mismatch. Cookie requests require Origin, X-Katara-CSRF and the mounted X-Katara-Account-ID. No query parameters are accepted. Recover a lost acceptance reply with the original body and Idempotency-Key; a completed replay requires the original token hash and current active recipient membership/account, without reviewing or consuming the invitation again. Secrets and review bodies are not saved in operation metadata.
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.
Required for cookie-authenticated changes. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{ "token": "example", "expected_digest": "example", "expected_version": 1}Responses
Section titled “Responses”Successful request
object
Examplegenerated
{ "operation_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "resource_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "completed": true}The reviewed state or request changed, or the cookie account differs. Reload and review; never replace an uncertain acceptance request automatically.
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" }}