What it does
A platform other people build on needs a surface they can rely on. This is designed as typed access to the same modules the first-party applications use — issuance, compliance, register, payments, reporting — so a partner building their own front end is not working against a lesser version of the platform. Versioned, documented, and with the same permissions model applied to an API call as to a click in the console. In development.
Powers
How it works
The API & SDK is how everyone else builds. Module Composer assembles the platform, this exposes it, and Monitoring & Alerting watches what partners run on it.
Select a step to replay it. Hover to pause.
Step 1 of 3: Integrate. A partner installs the client library and authenticates against their own permissions.
Key capabilities
Typed client libraries
The shape of every call is described, so mistakes surface at compile time.
Same modules the apps use
Partners are not given a reduced surface while the first-party apps use a better one.
Versioned and documented
An integration written today keeps working, and changes are announced rather than discovered.
Permissions apply equally
An API call is subject to the same authorisation as the same action in the console.