Authentication model
Use server-side, scoped credentials; never expose secrets in browser code.
Planned — contact supportDevelopers / API and SDK
VirtusCloud’s API direction covers business records such as customers, invoices, payment links, payments, and events. Access is not presented as a generally available public API today.
Talk to our teamPublic API and SDK access requires approval and is currently a contact-support capability.
What changes for your team
Use scoped credentials
Work with stable record IDs
Receive supported events
Build against explicit contracts
Capabilities
Use server-side, scoped credentials; never expose secrets in browser code.
Planned — contact supportProposed endpoint family for creating and retrieving approved customer data.
Planned — contact supportProposed endpoint family for operational billing and collection records.
Planned — contact supportRead transaction outcome and associated business context where access is approved.
Planned — contact supportReceive signed events for supported record and payment changes.
Planned — contact supportOfficial language SDK availability is not currently claimed.
Planned — contact supportEnd-to-end workflow
Describe the application, required records, data direction, and operating owner.
Define credentials, environments, allowed operations, rate expectations, and event handling.
Keep secrets out of clients and validate all inputs and webhook signatures.
Monitor failures, rotate access when required, and update against documented version changes.
Where it fits
Generate an approved payment or invoice record from an upstream business workflow.
Bring approved customer or billing state into another operating surface.
Use signed event delivery to trigger a controlled downstream process.
Questions
No. API access is currently planned or approved case by case through support.
Sensitive credentials must remain server-side. Client applications should call their own protected backend.
Continue exploring