These endpoints power the Grantiva dashboard. They use cookie-based sessions — the browser sends credentials with
credentials: 'include' and Vapor manages the session cookie. They are documented here for completeness; server integrations should use API keys instead.The auth response object
Login,me, verify-email, switch-org, and clear-org all return the same shape:
organization and entitlements are null when the user has no organization context. Null values inside limits mean unlimited.
Log in
200 OK — the auth response object.
Errors
Log out
204 No Content.
Current user
aat_, grantiva_, or gpat_ prefixed) and returns a minimal identity instead:
401 if neither a session nor a valid key is presented.
Forgot password
Reset password
Change email
Confirm email change
400 for an invalid/expired token, 409 if the address was taken in the meantime.
Verify email
Accept a team invite
List organizations
isActive marks the org currently selected in the session.
Response
Switch organization
403 otherwise); 404 if the slug doesn’t exist.
Request body
Clear organization
organization and entitlements set to null.
See also
- CLI Sessions — device-code auth for the Grantiva CLI
- API Keys — server-to-server authentication