Skip to main content
Use the Talaria Directory API to resolve decentralized identifiers (DIDs) and submit authorized changes to public DID records.
This reference documents only the public API contract.

​
Base URL

Use the HTTPS URL provided by your Talaria Directory operator.
The hostname in this documentation is a placeholder. Replace it with your operator-provided hostname. The API playground is disabled so examples cannot send requests to the placeholder. Send JSON request bodies with the Content-Type: application/json header. URL-encode DIDs, aliases, and document component IDs when you place them in a path.

​
API groups

DIDs

Resolve, register, and update public DID records.

Aliases

Add, update, and remove public aliases.

DID documents

Manage verification methods, authentication, key agreements, services, and the root key.

Delivery policies

Set public recipient, tag, and persona delivery policies.

​
Submission behavior

Mutation endpoints return 202 Accepted after the Directory accepts a request for processing. This status does not confirm final settlement. Accepted submissions return a public receipt containing the affected DID, operation name, transaction hash, and a human-readable message.

​
Errors

Newer endpoints return JSON errors with error and message fields. A details object appears only when the server has safe public context to return.
Do not log private keys, signing material, or unredacted authorization payloads. Public keys, DIDs, aliases, policy documents, and service endpoints may become publicly discoverable.