Dingo APIs and Archive Services

Application APIs

Dingo’s Blockfrost-compatible REST, Mesh/Rosetta REST, and UTxO RPC interfaces serve application clients. They require storageMode: api, which stores historical transaction data for queries. Configure each listener under plugins.api; set its port to 0 to disable it.

Interface	Protocol	Default port
Blockfrost-compatible API	HTTP/REST	3000
Mesh (Rosetta)	HTTP/REST	8080
UTxO RPC	Connect/gRPC and HTTP	9090

For example, enable the built-in Blockfrost and UTxO RPC providers in dingo.yaml:

storageMode: api
plugins:
  api:
    blockfrost:
      provider: builtin
      config:
        port: 3000
    utxorpc:
      provider: builtin
      config:
        port: 9090

The complete v0.73.4 configuration reference and release-matched dingo.yaml.example are available on this site. Use configuration files with their matching release; provider options can change between versions.

Secure API access

The api.tls and api.auth settings define shared defaults for the selected API providers. A provider can override either policy under its own plugins.api.<name>.config block. Authentication is disabled by default. When token authentication is enabled, send Authorization: Bearer <token>; Blockfrost clients may also use the project_id header. UTxO RPC’s HTTP and Connect/gRPC routes use the bearer token as well.

Authentication applies to every route on that listener, including health checks. Configure a probe to send the token or use a TCP check when the probe cannot attach credentials. Dingo rejects incomplete TLS certificate/key pairs at startup and does not log token or key contents.

You can also put API listeners behind a reverse proxy or API gateway. Choose one place to terminate TLS and authenticate requests, and configure Dingo’s listener policy to match that deployment.

Bark archive traffic

Bark is a Dingo-to-Dingo archive protocol, separate from the application APIs. An archive node can serve historical blocks from signed-URL-capable object storage. A history-expiry node can use a Bark archive as a fallback after old local block files expire; see Bootstrap and data maintenance.

Bark has no built-in authentication for ordinary archive traffic. Keep it on a trusted network. If you enable the database lifecycle service, follow the configuration example’s mutual TLS requirements for its maintenance RPCs.