跳转到内容

Device API Overview

Device authorization API for public clients.

Public clients use the Device API to obtain a device code, send the user to browser approval, and poll for ordinary Sudomimus application tokens. No client secret is required. After issuance, use the Session API to refresh, inspect, or revoke the resulting session. Browser approval confirms platform Basic Terms separately from application sharing consent. A valid existing platform receipt skips the terms step. Accepting platform terms does not create application-sharing decisions. Browser Auth API responses also carry a server-owned flowTasks snapshot. This browser presentation contract does not change Device API polling. Device approval follows any remaining application consent and required-data repair steps. Polling continues to return authorization_pending meanwhile. During browser approval, email discovery offers OTP only when the requested owned address has an enabled email-OTP credential. An OTP credential for another address on the same account does not enable that option. Before account proof succeeds, the browser may cancel its exact email OTP challenge through Auth API and edit the address in the same approval flow. Cancellation invalidates the old code and retains the session expiry, cooldown, delivery limit, comparison budget, and discovery budget. It cannot switch accounts after proof, including while terms or consent are pending.

Information

  • License: MIT
  • OpenAPI version: 3.1.0