Sequence · Diagram Design · Special

Bearer call with refresh

A resource call under a bearer token, with an ALT fragment for the happy path versus a 401 that refreshes via Auth and retries. Async audit is fire-and-forget with an open arrowhead.

Bearer call with refresh Client calls API with a bearer token. An ALT fragment shows either a valid 200 response or a 401 path that refreshes via Auth and retries. GET /RESOURCE + BEARER ALT [token valid] 200 · BODY [else · 401] 401 POST /TOKEN · REFRESH 200 · NEW ACCESS GET /RESOURCE · RETRY 200 · BODY AUDIT · ASYNC APP Client SPA · SDK API Resource API Bearer gate AUTH Auth token · refresh LEGEND Focal / success ALT Fragment HTTP call Return Async open Headline

THE HEADLINE

Valid token is one hop

When the access token is still good, the ALT frame collapses to a single coral return. That is the path most readers should see first.

401 drives refresh

  • API answers 401, not a hard fail
  • Client posts refresh to Auth
  • New access returns dashed
  • Retry re-enters the resource API

Async uses open arrows

The audit event is dashed with an open arrowhead so it never reads as a blocking return. Returns stay filled even when dashed.

oauth · bearer + alt refresh sequence example · schematic skill