Assetera Docs
Integrate

Integrating with Assetera

Connect as a distribution partner. The two integration modes, the tenant model, and where the token flow is documented.

Assetera is a B2B2C platform: regulated institutions offer Assetera's tokenized instruments to their own customers through one shared, multi-tenant Marketplace API. You are provisioned as a tenant of that API (not a bespoke deployment), and everything you see is scoped to your tenant.

Before integrating, read Tenancy & responsibility: it covers how a tenant is resolved and who is responsible for KYC/AML under a reliance vs a tied-agent arrangement.

Two ways to integrate

How your customers reach the API depends on whether you bring your own frontend:

Assetera-hosted UIYour own frontend
Best forturnkey partners, no frontend to buildpartners with an existing product
Users sign in viaAssetera-hosted pagesyour app → Assetera Identity (redirect)
Token handlingAssetera's backend holds tokens server-sideyour backend holds tokens server-side (BFF)
Also supports(n/a)machine-to-machine (client-credentials) for backend-only flows

In every mode the browser never holds an access token, and the API validates the same token contract: a signed token carrying { tenant, subject, audience, scopes }. The mode only changes how the token is obtained, not how it is validated.

The end-to-end journey

Whatever the mode, one customer's path through the platform is the same. Sign-up and KYC run against Assetera Identity; browsing, trading, and settlement run against your tenant's slice of the Marketplace API.

The tied-agent walkthrough shows how to wire this journey into your own Next.js app end to end.

Next

On this page