List supported networks
Lists every network OMS supports, with its identifiers, available assets, and which OMS resources can use it in which direction. Availability is derived from live route configuration, so a network absent from this list is not routable; the fiat-rail availability and the crypto deposit-address signal both reflect your own project’s provider configuration.
A project can hold more than one payment provider. Omit vendor and the response is the union of every provider the project holds, which over-reports for a caller that already knows which provider a given customer belongs to. Pass vendor to scope the response to exactly that one. It must be a provider the project actually holds, and one of coinme or erebor; anything else is rejected with 400 (error InvalidParameter, code 10006) rather than falling back to the union.
“Network” here means any rail, not only a blockchain: category (crypto | fiatAccount | cash) and type (blockchain | bankRail | card | physical) are what distinguish them, and chainId / networkFamily are absent on everything that is not a blockchain.
Authorizations
Token from POST /auth/token
Query Parameters
Scope the response to one vendor the calling project holds. Omit to get the union of every vendor the project has.
The payment provider a project routes through: coinme is Coinme Inc., erebor is Erebor Bank, N.A. Pass it as vendor on GET /networks to scope that response's supportedBy signals to one provider; omit it and the response is the union of every provider your project holds.
coinme, erebor