Finance · security identity
Pushed Authorization Requests (PAR)
Pushed Authorization Requests (PAR), defined in RFC 9126, let an OAuth 2.0 client send its authorization request parameters directly to the authorization server over a secured back channel and receive a request URI to use at the authorization endpoint. This keeps request parameters off the front channel, protects their integrity, and is a required building block of the FAPI security profiles used by open banking and open finance.
Also known as PAR, RFC 9126, OAuth 2.0 Pushed Authorization Requests.
Providers that carry Pushed Authorization Requests 0
No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements Pushed Authorization Requests and says so in its APIs.json profile appears here on the next build. Add or correct a listing.
Read from the API Evangelist standards directory. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.