Developer documentation
Build against a real Directory of Participants
Directory implements the participant-registry pattern used by production Open Finance directories (UK Open Banking, Open Finance Brasil, PSD2 eIDAS-based ecosystems): mutual TLS, RFC 7591 dynamic client registration, JWS-signed software statements, and a public, versioned API. This section documents how to integrate with it.
/Key components
Trust anchor
Directory operates its own CA and JWS signing key. Every participant certificate chains to the CA published at GET /ca-certificate; every software statement is signed with the key published as a JWK Set at GET /jwks.json.
Participant registry
GET /organisations and GET /participants expose every active participant, their authorisation servers, certificates and software statements — unauthenticated, versioned, and always current.
/Where to start
Getting started
Register an institution, complete its profile, and activate it — with real request/response examples.
Registration & validation
What the functional validation step actually checks, and why declaring capabilities isn't enough.
Certificates & mTLS
Certificate lifecycle, and how sessions/credentials get bound to a client certificate (RFC 8705).
Web console
Every capability described here, also reachable from a browser — no client to write for day-to-day administration.
Security
Password and passkey authentication, sender-constrained tokens, and a durable audit trail — how each is actually enforced.
API reference
The full OpenAPI 3.0.3 specification, rendered from the same file the running instance serves.