organisation.invites.accept

mutation write

Use when the requested change exactly matches organisation.invites.accept; read the current state first when a version or identifier may have changed.

Before calling

• Authenticate as the accountable Enhance person.
• Use only resource identifiers returned by an earlier capability result or supplied by the person.
• Reuse clientToken only when retrying this exact mutation input.

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    }
  },
  "required": [
    "token"
  ],
  "additionalProperties": false
}

Example

{
  "token": "x"
}

Result

Returns a typed organisation.invites.accept result from the Enhance API without transport-specific prose.

Recovery

• BAD_REQUEST: correct the named fields and call again.
• UNAUTHORIZED: restore Enhance authentication, then retry once.
• FORBIDDEN or NOT_FOUND: list accessible resources and choose an allowed identifier.
• CONFLICT: read the current resource, merge the intended change, and retry with its version.
• INTERNAL: run Enhance diagnostics, report the failure, and stop repeating the call.

Continue with

• Read the affected organisation resource to confirm the result.

Compatibility: 91882d9637e521d1913226474155f38d2885344f54ad2aff3220db5aa3dc1e0c.