v1.0.0
OpenAPI 3.1.1

Stellari API — Merchant Reference

Stellari API for merchants — manage payment methods, balances, transactions, payment requests, webhooks, and API keys.

Authentication: All endpoints require either a JWT Bearer token or API Key (HTTP Basic). See the Authentication section for details.

Error format: All errors return {"error": {"code": "...", "message": "...", "type": "..."}}.

Pagination: Cursor-based with limit + cursor query parameters. Responses include has_more and next_cursor.

ID prefixes: ent_ (Entity), pmr_ (PaymentMethod), bal_ (Balance), lde_ (LedgerEntry), txn_ (Transaction), prq_ (PaymentRequest), ak_ (ApiKey), whs_ (WebhookSubscription), wdl_ (WebhookDelivery), iet_ (IntegrationEventType), iev_ (IntegrationEvent).

Sandbox

No authentication selected
Client Libraries

Authentication (Collapsed)

​

Signup (Collapsed)

​

Password Management (Collapsed)

​

Auth Tokens (Collapsed)

​

OTP resend

Auth Tokens Operations

Permissions (Collapsed)

​

Effective role-based permissions for the authenticated caller. The front-end uses this to gate UI; backend handlers enforce the same matrix via #[RequiresPermission] on Commands/Queries.

Permissions Operations

Addresses (Collapsed)

​

Balances (Collapsed)

​

Recipients (Collapsed)

​

Search recipients by email or alias for wallet-to-wallet transfers

TaskEvents (Collapsed)

​

Mercure SSE stream for async task events

ServerStatus (Collapsed)

​

Server health check

ServerStatus Operations

API Keys (Collapsed)

​

Create and manage API key pairs for programmatic access to any Stellari endpoint

Webhook Deliveries (Collapsed)

​

View delivery history, inspect attempts, and redeliver events

Webhook Catalog (Collapsed)

​

Browse available webhook event types

Webhook Catalog Operations

Currencies (Collapsed)

​

Currency catalog

Currencies Operations

Notifications (Collapsed)

​

Backoffice notification inbox — list, mark as read, and bell badge count. Powered by a catalog-driven projector that listens to IntegrationEventPublished and writes per-merchant or platform-wide entries.

Notification Subscriptions (Collapsed)

​

Per-merchant preferences over which notification types are delivered. Defaults live in the catalog (8 ENTITY-scope event types, 4 default-on, 4 default-off). Merchant overrides are stored only when the merchant explicitly toggles a type.

Recurring Transfers (Collapsed)

​

Merchant-owned recurring fiat transfers (STELL-139). Wallet → recipient entity, cron-scheduled, with optional expiration / max executions. Each recurring is independently pausable / cancellable; cancellation is terminal but preserves dispatch history.

Scheduled Transfers (Collapsed)

​

One-shot future-dated fiat transfers (STELL-144). Wallet → recipient entity, fires exactly once on scheduled_for then transitions to a terminal state. Available to both merchants AND individuals.

Contracts (Collapsed)

​

Provider contracts attached to an entity: which transaction types, rails, currencies and countries it covers, with its fees and settlement model. Listing requires canViewContracts and creating requires canCreateContract; neither is granted to merchants by default.

Health (Collapsed)

​

Unauthenticated liveness (/health) and readiness (/health/deep) probes for monitoring. No authentication required.

Models