Add a member to a vault
Give someone a role in a vault. Name them by user_id or by email, exactly one of the two.
The person has to be a member of your organization already. An address that belongs to nobody in the organization returns 400 and nothing is sent, so this endpoint can never invite anyone or add a seat.
Adding someone who already holds a role returns their existing row unchanged, current role included. That keeps a repeated call from quietly demoting an owner to editor. To change a role, use PATCH /vaults/{id}/members/{userId}.
Requires the owner role in the vault and the organization-level permission to manage vaults.
Requires a user-scoped API key (u:gcai_...). A vault is shared with named people, so an organization-scoped key has no identity to resolve vault access with.
Request
- Base URLhttps://app.gc.ai/api/external/v1
- AuthAPI key in header Authorization
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
The vault ID
Request body
Example request
{
"email": "dana@example.com"
}Response
The vault member
Changes
No recorded changes to this operation across all 1 revision of this API.