Login

Providing what is needed for existing API consumers to login and access their accounts, keys, and other information regarding their API consumption. A login allows any consumer of an API to be able to access the resources they will need to make a decision when it comes to integrating, expanding, or deprecating their usage of an API, providing what consumers will expect.

Also known as: Sign In, SSO, Authentication UX, Session

Example

login.yaml
- type: Login
  url: https://developers.example.com/login

Standards

HTTP Headers

HeaderDirectionSpecDescription
Authorization request RFC 9110 §11.6.2 Bearer or session-bound tokens issued at login.
Set-Cookie response RFC 6265 Session cookies issued post-login; use Secure, HttpOnly, SameSite.
Cookie request RFC 6265 Client returns the session cookie on subsequent requests.
WWW-Authenticate response RFC 9110 §11.6.1 Challenge that may redirect users into a login flow.

Status Codes

Well-Known Paths

Media Types

OpenAPI Expression

Link Relations

Governance Rules

Risk & Compliance

OWASP:

Compliance:

Security: Login is the highest-value attack surface. Use PKCE for all OAuth clients (RFC 9700), redirect-URI exact matching, anti-CSRF on form posts, phishing-resistant factors (WebAuthn/passkeys), short access-token lifetimes with refresh-token rotation and reuse detection, account-lockout/back-off against credential stuffing, and device/browser fingerprint anomaly checks.

Tools

Suggested Metrics

Example Implementations

Related Properties

Tags


All Common Properties