API reference · Auth
List identities
Which sign-in methods this account has.
- Authentication
- Bearer token
- Retries
- Safe to repeat
- Body
- None
- Version
- 2026-09-03
Shown on the security page, and what the dashboard needs in order to grey out "disconnect" on the only one left.
Responses
- 200OKapplication/json
array of IdentityRead — each item has these fields
created_atstring (date-time)requiredproviderstringrequiredemailstring | nulllast_login_atstring (date-time) | null
5 response headers
- RateLimit-Limit
Requests permitted in the current window.
- RateLimit-Remaining
Requests left in the current window. Back off before it reaches 0.
- RateLimit-Reset
Seconds until the current window resets.
- X-API-Version
The dated version of the API contract that served this response, e.g.
2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.- X-Request-ID
Quote this in a support request to identify the call.
Example request
curl "https://api.integrable.cloud/api/auth/identities" \
-H "Authorization: Bearer $INTEGRABLE_API_KEY"Set INTEGRABLE_API_KEY first. The same call from the TypeScript or Python SDK takes the same fields.
Example response
[
{
"created_at": "2026-09-03T09:30:00Z",
"email": "sam@example.com",
"last_login_at": "2026-09-03T09:30:00Z",
"provider": "string"
}
]Generated from the schema above — the shape is exact, the values are placeholders.
Errors
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-bot limit on top.
More Auth endpoints
- post/api/auth/accept-invitationAccept invitation
- post/api/auth/change-passwordChange password
- post/api/auth/forgot-passwordForgot password
- post/api/auth/googleComplete Google sign-in
- get/api/auth/google/startStart Google sign-in
- delete/api/auth/identities/{provider}Unlink identity
- get/api/auth/invitationPreview invitation
- post/api/auth/loginLog in
- post/api/auth/logoutLog out
- post/api/auth/logout-allLog out everywhere
- get/api/auth/meGet the current user
- get/api/auth/mfaMFA status
- post/api/auth/mfa/activateActivate MFA
- post/api/auth/mfa/disableDisable MFA
- post/api/auth/mfa/recovery-codesRegenerate recovery codes
- post/api/auth/mfa/setupSetup MFA
- post/api/auth/mfa/verifyVerify MFA
- get/api/auth/organizationsList my organizations
- post/api/auth/otp/requestRequest OTP
- post/api/auth/otp/verifyVerify OTP
- post/api/auth/refreshRefresh a session
- post/api/auth/registerRegister an account
- post/api/auth/resend-verificationResend verification
- post/api/auth/reset-passwordReset password
- get/api/auth/verification-statusVerification status
- post/api/auth/verify-emailVerify email
Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.