Check Login Exists
Checks whether a login (e-mail) already exists for the organization. Strict match on (organization, login) — the unique key of a connect user, without the dev fallback. Used to validate user creation before creating the person, avoiding an orphan person when the e-mail is already in use as a login.
Try-it values populated from environment ACME (Demo)
Authentication
Token
Most Connect endpoints require a valid x-guper-authorization token.
Token issuance itself (/api/connect/auth) is the exception — it
uses the x-guper-apikey and x-guper-apisecret credentials.
Headers
Query parameters
Responses
Copied to clipboard