OpenAPI 3v2 REST

Build on SwilUnify like a product team

This reference covers Transactions, Reports, and GET /app-keys/validate (app key check). Types and examples come from the live OpenAPI document; Swagger UI on the API host still exposes the full server specification.

Interactive Swagger UI Download openapi.json

Live surface

Point clients at the same host you select for examples below.

Base URL

—

Operations

—

Schemas

Tenant-safe by design

Every route is authored for multi-tenant isolation. Tokens and keys carry company context so integrators never cross streams.

Operational clarity

Predictable envelopes, explicit error codes, and first-class documentation for batch CSV flows and real-time exchanges alike.

Curated for integrators

Documentation here is intentionally scoped to exchange and reporting APIs plus app-key validation—so partners see exactly what they need without wading through the entire control plane.

Quick start

Create a user via POST /auth/register or sign in through the hosted app, then capture the JWT from POST /auth/login.
Issue an API key from the company admin console when you need server-to-server automation (x-api-key).
Pair platform calls with x-app-key when integrating SwilUnify marketplace features.

Authentication patterns

Choose the credential model that matches your deployment topology.

Browser and mobile clients should use short-lived JWTs. Send Authorization: Bearer <token> on every request after login.

Schema explorer Copy-ready examples Transactions focus

SwilUnify API reference

Transactions, Reports, and GET /app-keys/validate—filtered from the live OpenAPI document. Pick an environment, use Inspector on any operation for a side panel with cURL and JSON, or expand the card for full tabs.

0 documented operations

Loading OpenAPI specification…