Check PID handle availability
Returns whether `handle` is free (`<handle>@pid`). Used by the onboarding handle picker before starting Google sign-up. Handles are lowercase `^[a-z0-9_]{3,20}$`; the full PID is `<handle>@pid` — permanent, never changeable, reused, or reassigned.
Returns whether handle is free (<handle>@pid). Used by the onboarding
handle picker before starting Google sign-up. Handles are lowercase
^[a-z0-9_]{3,20}$; the full PID is <handle>@pid — permanent, never
changeable, reused, or reassigned.
Query Parameters
^[a-z0-9_]{3,20}$Response Body
application/json
application/json
curl -X GET "https://example.com/auth/pid/available?handle=string"{ "available": true, "pid": "ifal@pid"}Redirect to Google OAuth consent screen GET
Redirects (HTTP 302) to Google's OAuth consent screen with `scope=profile email`. **Browser-navigation only.** Open the URL in a browser tab (top-level navigation); it cannot be called via `fetch()` or the Swagger "Send" button — the cross-origin redirect to Google is blocked by CORS and appears as `Failed to fetch`, which is expected. Not meant to be called directly by clients — use `POST /auth/login` to obtain the URL.
Mint a pid_code for the current session POST
Issues a one-time pid_code for the caller's existing session — no re-authentication. Powers consent screens on PeridotID-hosted pages: the user approves, the page redirects itself to returnTo with the code. Cookie-authenticated (same-site pages only). returnTo follows the same rules as login (loopback, registered app origins, global allowlist).