Change an invitation's permission group
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/team-invitations/v1-invite-update-put.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
PUT/
Changes which permission group the person will join with. No email is sent.
The path takes the invitation's id from the list: a UUID, not a hash id.
Use PUT. PATCH has no rules and fails with 500.
An expired invitation is left as it is, and the call still succeeds: check expired in the response.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The invitation's
idfrom the invitation list: a UUID, not a hash id.- Example
0b5e8c1a-3f4d-4c2b-9a7e-1d2c3b4a5f60
- Example
Request body
application/json, required.
One of this team's permission groups, from
GET /v1/api/store/{team_slug}/setting/group.
Response
200Successful response.
Child fields (5)
True two months after the invitation was first created.
When it expires: two months after it was created. Resending does not move this date.
The invitation's id: a UUID, not a hash id. Use it in the invitation paths.
roleobject | nullThe permission group the person will join with. Null if that group was deleted since.
Child fields (5)
The group's permission keys, as "Get a permission group" returns them.
The members who already hold this group.
Fields of each item (4)
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- Your role lacks Manage Settings. The body is
{"message": "Insufficient Permission"}, without the error envelope. - Fix
- Use the key of a member whose role has Manage Settings, or the owner's.
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- No invitation of your team has this id.
error.codeis null;error.messagenames the record type. - Fix
- Use an
idfrom the invitations list. - When
role_idis not one of your team's permission groups.error.codeis null;error.messagenames the record type.- Fix
- Use a group id from the groups list.
422The request was refused and changed nothing.
validation_failedlists what to fix inerror.fields; other codes name a business rule, explained inerror.message. A few checks answer with only{"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answerconnect_timeout("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.- When
role_idis missing or not an id (validation_failed).- Fix
- Send a group id from the groups list.
Related
- GETList invitations
/v1/ api/ store/ {team_slug}/ setting/ invite - GETList permission groups
/v1/ api/ store/ {team_slug}/ setting/ group
