API reference
The integrator-facing Assetera interfaces for authentication, marketplace operations, compliance status, and real-time updates.
Assetera exposes standards-based OIDC authentication, REST APIs, and a ticketed Server-Sent Events stream. Availability and permissions are tenant-specific.
Surface at a glance
| Surface | Purpose | Contract |
|---|---|---|
| Authentication | User sign-up and sign-in, service authentication, federation, and restricted token exchange | OIDC discovery |
| Marketplace API | Tenant catalog, markets, orders, offers, activities, and enabled primary-sale flows | Live OpenAPI and Swagger UI |
| Compliance API | Customer-scoped onboarding status, SDK sessions, and wallet registry | Live self-service API; access is provisioned |
| Real-time SSE | Ticketed public and customer updates without exposing the user's API token | Live where enabled |
Contract rules
- Resolve environment endpoints from the tenant handover or OIDC discovery. Do not hardcode hosts.
- Keep OAuth credentials and API tokens in your backend or BFF.
- Treat the published OpenAPI document as authoritative for paths and payloads.
- Expect permissions, audiences, and enabled resources to differ by tenant.
- Reconcile real-time messages against REST snapshots after reconnecting.
Authentication
OIDC, tenant context, federation, and wallet token exchange.
Marketplace API
REST resources and the live OpenAPI contract.
Primary sale API
The three primary-sale rails, the quote lifecycle, and the refusal codes.
Compliance API
Customer-scoped KYC and wallet endpoints.
Real-time SSE
Mint a scoped stream ticket, then connect with EventSource.
How Assetera works
The platform at a glance: standards-based identity, one multi-tenant Marketplace API, on-chain settlement, and a compliance layer Assetera runs in every partnership model.
Authentication (OIDC)
What credentials a tenant receives, how to use them, and what they represent. Assetera Identity speaks standard OIDC / OAuth 2.0, so any conforming client library works.