Resolution Steps
The user or an API sends a GET request or inserts a W3C did:web address in the input field and the API resolves the did:web accordingly.
Example Request Pipeline
To initiate the resolution pipeline, you can either pass the string via the interface or call the gateway directly via HTTP GET:
The resolver targets the host domain over safe HTTPS, requesting the standardized root W3C DID asset definition. Following the W3C did:web specification, the API targets either the .well-known path or a subfolder path determined by the DID structure. This step is successful if the API receives a valid JSON file.
Example valid JSON file
The core backend verifies the document structure and checks the requested mode. With s=did (or the existing service=did-only form), the API returns the raw DID JSON immediately. For other modes, the engine proceeds to the next step.
The engine queries the decentralized storage endpoints for secondary payloads. With s=com (or the existing service=com-reg form), it redirects to the matching commercial register endpoint; otherwise, the workflow is aborted if no valid sub-resource endpoint can be routed. Use s=dpp (or service=dpp-only) for raw DPP JSON.
Example valid service enpoint
With no query parameter, or the existing service=dpp and service=dpp-ui forms, the system evaluates the payload metadata (like the renderMethod) and returns an HTTP redirect for the visual view.