Skip to main content
These docs describe only the network interfaces that application developers need to build compatible Talaria clients.

​
Public developer APIs

The examples explain HTTP methods, paths, fields, encodings, signatures, responses, and errors. You do not need to understand how a node stores data or communicates with other nodes.

​
What is intentionally excluded

This reference does not describe:
  • Private keys, seed phrases, or account secrets
  • Administrative cleanup or maintenance operations
  • Health checks intended only for operators
  • Mesh bootstrap, gossip, or node-to-node coordination
  • Internal persistence, queues, retry implementation, or database design
  • Chain RPC credentials or server signing configuration
  • Test-only and legacy compatibility routes
A legitimate public Talaria endpoint never needs your private key or seed phrase. Sign locally and send only the resulting public payload and signature.

​
Public does not mean unencrypted

DIDs, public keys, aliases, service endpoints, and delivery policies may be publicly discoverable. Message contents should remain encrypted inside the DDN envelope. Relay and Cache nodes route or store the envelope without needing to decrypt its payload.