CantonCapDocsExplorer

Connector capabilities

Canton venues differ in what they expose and to whom. The capability matrix publishes exactly what each connector can answer.

There are 17 canonical methods. For every venue, each method reports whether the source documents it, whether this deployment has bound an implementation, what access it requires, and what scope its results carry.

http

GET /v1/venues/{venue_id}/capabilities

Available is not the same as implemented

  • available — the reviewed source contract documents enough data to satisfy the method.
  • mode — native, derived, local or unavailable. Documented capability can legitimately precede a bound implementation.
  • access — public, api_key, invite_jwt or partner_required.
  • scope — whether results are public-market, caller-visible or party-scoped.

Unsupported is not failing

A venue awaiting a partner contract reports every data method as unavailable. That is a documented posture, not an outage, and it should not be surfaced to your users as an error. Use GET /v1/status/sources for runtime health, and the capability matrix for what is structurally possible.