Skip to main content
Talaria provides a public Directory API for resolving decentralized identifiers (DIDs) and submitting authorized updates to public DID records. Use this reference to create an identity, register its DID document, resolve public records, and manage aliases, document components, devices, and delivery policies.
These docs cover only the public API contract. They exclude operational interfaces and Talaria’s internal validation, persistence, signing, routing, and chain implementation.

​
Start building

Create your first DID

Generate an Ed25519 keypair, DID document, and signed registration request from Bash or Python.

Directory API overview

Learn about the public endpoint groups, submission behavior, and error format.

​
Explore the API

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 root keys.

Delivery policies

Set public recipient, tag, and persona delivery policies.

​
Base URL

Your Talaria Directory operator provides the HTTPS base URL for API requests:
The hostname in these docs is a placeholder. Replace it with the hostname supplied by your operator.

​
Request lifecycle

  1. Generate an Ed25519 keypair and a Base58 Talaria DID.
  2. Build a public DID document that contains the public key.
  3. Sign the registration request with the private key.
  4. Submit the request to POST /register-did.
  5. Resolve the DID until its registration_status is confirmed.
Never send your private key to the Directory. Store it securely and submit only public keys, signatures, and public DID document data.