Login
Login
Authenticate a reader and return a session token
POST
Login
Authenticates a reader and returns an opaque session token. Supports two flows — email/password and OAuth (Google, Facebook) — on the same endpoint. The active flow is determined by the presence of the
Email / password flow — omit
OAuth flow — include
The full raw body is forwarded to the backend as JSON.
The full raw body is forwarded to the backend as JSON.
client field.
Your Publisher ID
Use
Content-Type: application/json for OAuth logins. For email/password, both application/json and form encoding are accepted.client
Reader’s email address. Normalized to lowercase before forwarding.
Reader’s password.
reCAPTCHA token from the client widget. Only applicable to this flow. Required when your publisher has a
login_captcha.secret_key configured.client to switch to this path. password is not accepted in this flow.
OAuth provider. Accepted values:
google, facebook. Presence of this field activates the OAuth flow.Email from the OAuth provider. Required when using OAuth. Normalized to lowercase.
Google OAuth — extra fields
Google OAuth — extra fields
| Field | Type | Description |
|---|---|---|
sub | string | Google subject identifier |
name | string | Full name |
given_name | string | First name |
family_name | string | Last name |
picture | string | Profile photo URL |
email_verified | boolean | Whether Google has verified the email |
hd | string | Hosted domain (G Suite accounts) |
Facebook OAuth — extra fields
Facebook OAuth — extra fields
| Field | Type | Description |
|---|---|---|
id | string | Facebook user ID |
name | string | Full name |
first_name | string | First name |
last_name | string | Last name |
picture | object | Profile picture object |
Last modified on June 5, 2026