GET /v1/catalog
The deployment’s declared corridor registry — build pickers from it rather than from a hand-kept
table. Open to your project id, so a page’s pickers render before your user signs in to anything.
Built once at boot from configuration; it changes only on restart. The external aggregator lanes
are not listed (quoting is their discovery).
Request
No path, query or body parameters.Response
data (Catalog): {chains[], assets[]} — both always arrays.
chains[], sorted by domain:
assets[], sorted by chain then key:
Behavior
Open to a project id — a page’s pickers render before your user signs in to anything. Built once at boot from configuration; it changes only on restart. The external aggregator lanes are not listed (quoting is their discovery mechanism).Errors
The handler itself never fails, so this route answers noEIN code, not even EIN0049.
The gateway’s own refusals — a refused credential or origin, a rate limit, the hub unreachable or
too slow — can come back, with an EPX code and a real HTTP status
(Errors — gateway codes).
Example
Response
Illustrative values; formats follow the Response table.eip155-56 omits userProxy/swapRouter/nativeKey/wrappedKey (none declared, omitempty); the eth row is the chain-native zero-address declaration, flagged illustrative.
The values above are illustrative fixtures. Read the live set from your deployment; how to read
the rows is on Supported chains and assets.
See also
- SDK:
client.getCatalog(), aCatalogIndexwith lookups for pickers and the checks - Quickstart