API Reference

The Seismic Orchestration API. All endpoints live under /api/v0/*. Paths in the per-endpoint pages drop the /v0/ prefix for readability. Curl snippets throughout assume $SEISMIC_ORCHESTRATION_URL and $SEISMIC_ORCHESTRATION_API_KEY.

Two audiences in one API

Two cohorts of humans + records flow through this API. They never overlap:

• You and your org. The integrating partner: your team's dashboard logins, your org-scoped API keys, your KYB profile. Lives under Orgs and Auth below. "User" in this API always means a member of your org, not an end-customer. That's GET /auth/me.
• Your end-customers. The individuals or businesses your product onboards, the people whose money is moving. Lives under Customers. They never log in to Seismic. You drive their KYC and attach their funding / payout accounts on their behalf.

Most production traffic lives under /customers, /accounts, and /quotes. The /orgs and /auth surfaces are the controls you (the integrating partner) use to manage your own access. You'll mostly hit them while building a dashboard.

Sections

• Orgs, /orgs/*: memberships, the organization KYB profile + state.
• Auth, /auth/*: signup, login, MFA, refresh, logout, /auth/me (whoami), plus API keys (mint / list / revoke).
• Customers, /customers: end-user customers owned by the org (NOT the org's own KYB; that's under Orgs). Includes /customers/:id/accounts for creating funding / payout accounts.
• Accounts, /accounts: read-side endpoints for the accounts created across the org's customers. Creation lives under Customers.
• Quotes, /quotes: ranked rail fan-out, explicit accept step, the richest surface we expose.
• Rates, /rates: mid-market reference rates, no quote required.
• Catalog, /rails, /schemas, and /currencies: unauthenticated reference of supported rails, named rail groups (us_bank, evm, …), and currencies.
• Errors: envelope shape, error codes, retry semantics.

Bridge compat

If you already integrated Bridge, we ship a best-effort compatibility layer at /api/compat/bridge/v0/* that mirrors Bridge's request / response shapes for the endpoints we implement (customers, KYC links, external accounts, transfers, exchange rates). A base-URL swap gets most integrations running without code changes.

Start here: Bridge compat overview.

The two surfaces share one Api-Key and one tenant: same account, two API shapes. If you're starting a new integration, use the native API above. The compat layer exists for existing Bridge callers.