Developers

This section is for engineers, technical due-diligence teams and partners who want to understand how the T-Suite platform works underneath: which services exist, how users authenticate, what the API surface looks like, how real-time updates are delivered, and which smart contracts back a tokenized offering.

If you are an investor, issuer or asset manager looking for how to use the platform, start with the User Manual instead.

Before you integrate

Status: Limited

Be clear about what exists today:

• There is no public, versioned API programme yet. The T-Suite API is the API that Libertum’s own web apps use. It is not published as a supported public product, and there is no maintained public OpenAPI reference.
• Integrations are by arrangement. If you want to connect a system to T-Suite (for example, a back-office, CRM or reporting tool), contact Libertum first so the integration can be scoped and supported.
• Endpoints can change. Paths, request bodies and response fields can change between releases without a deprecation period. Do not build production systems against undocumented endpoints without an agreement in place.
• Stablecoin Studio is the exception. It has a small, read-only developer API authenticated with issuer API keys — see API overview.

Nothing in this section is legal advice, and nothing here changes which licences Libertum group entities hold — see Licences.

What’s in this section

Page	What it covers
Architecture	Frontends, backend services, messaging (Kafka and gRPC), scheduled jobs, data stores and third-party integrations
Environments & networks	Production versus testing, mainnets versus testnets, and how testnet offerings are used for trials
Authentication	Sign-in, sessions, two-factor authentication, step-up verification for sensitive actions, server-to-server signing and tenant resolution
API overview	Base path, route groups, response envelope, status codes and rate limits
Real-time & webhooks	The Server-Sent Events notification stream, one-time stream tickets, reconnection guidance, and the current webhook position
Smart contracts	The ERC-3643 stack, Escrow settlement, ERC-20 and ERC-721 factories, Cardano and XRPL, the chain matrix and how to find contract addresses

Related reading

• Architecture & Integrations — the non-technical overview in the User Manual
• Token standards — what each token standard means for issuers and investors
• Compliance enforcement — how identity, jurisdiction and transfer rules are enforced end to end