Skip to main content
GET https://api.alentra.app/v1/catalog · Public · No API key · No charge
The canonical discovery ledger for jurisdiction, credential profile, presentation provider, onboarding requirements, rollout state, and runtime availability. Use it instead of hard-coding a country-to-wallet relationship: one country may have several routes, and one wallet provider may present credentials from several countries. The endpoint is public, CORS-readable, and cached for up to five minutes.

Response

string
Catalog response schema version.
string
Date the source-controlled coverage ledger was last verified.
string
development, sandbox, or production.
object[]
Every tracked jurisdiction. Coming-soon routes remain visible so absence and pending onboarding are distinguishable.
object[]
Fixed requirement records referenced by routes. Each includes a stable id, provider, label, mode (alentra_managed, alentra_managed_provider_review, or waitlist), whether customer action is required, customer/Alentra summaries, and an official source URL. These records explain onboarding; they do not make a route available.
object[]
Provider labels plus enabled (allowed by this deployment) and adapter_available (transport code registered at runtime).
object[]
Stable profile ids and their format, doctype, namespace, and fallback issuing country. Blank protocol fields mean onboarding/acceptance is incomplete and the profile cannot become available.
object[]
Legacy provider capability projection: provider id/label, adapter availability, and per-primitive booleans. Route selection must still use countries[].routes.
object[]
Shipped primitive ids and whether any registered provider adapter implements them.
The real response includes the full ledger, not only the Utopia excerpt above. Never offer a route unless its own available value is true; provider adapter availability alone is insufficient.