Skip to content
Seismic Orchestration

GET /schemas

A schema is a named group of rails. Reach for one when you want to say "any US-bank rail" on a quote without having to enumerate which rails are eligible today.

Unauthenticated. No Api-Key or Authorization header required.

Where schemas are used

Schemas are a query-time convenience. They're accepted in quote requests and surfaced as a derived field on Account responses (the named groups whose current expansion is fully contained in the account's rails).

They are not accepted on writes that declare a long-lived resource, notably POST /customers/:id/accounts, which takes explicit rails[] only. Attaching an account is a declaration. Schemas auto-expand at read time, which is the wrong shape for something you're pinning down.

Schemas resolve to the current rail expansion at request time. They do not freeze a point-in-time set.

Response 200

{
  "schemas": [
    {
      "schema": "us_bank",
      "kind": "fiat",
      "rails": ["ach", "wire", "swift"]
    },
    {
      "schema": "eu_bank",
      "kind": "fiat",
      "rails": ["sepa", "swift"]
    },
    {
      "schema": "evm",
      "kind": "crypto",
      "rails": ["base", "ethereum", "polygon", "arbitrum"]
    }
  ]
}

SchemaInfo

FieldTypeNotes
schemastringStable schema identifier: "us_bank", "evm", etc.
kind"fiat" | "crypto"Mirrors the rails it expands to.
railsstring[]Current expansion. Adds happen here when new rails land.

Example

curl "$SEISMIC_ORCHESTRATION_URL/v0/schemas"

See also