Onboarding, APIs and Ecosystem

what does a typical api led onboarding look like? most teams follow this path create workspaces and vaults, users and roles, attach policy templates, and destination allow lists/whitelisted addresses (which form your address book), wire webhooks and subscribe to event topics, reconcile using cursor based history, run testnet smoke tests, then launch with canary vaults in production and expand to exchanges and settlement everything you see in the ui is available over rest with the same policy and audit trail can we expose read only api users for analytics or the back office? yes you can create read only api keys that are scoped to the vaults and data you want to export, such as balances, transaction history, and snapshots these keys have no signing rights