Developers / API and SDK

Programmatic access, introduced with clear boundaries.

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 team
Planned — contact support

Public API and SDK access requires approval and is currently a contact-support capability.

What changes for your team

01

Use scoped credentials

02

Work with stable record IDs

03

Receive supported events

04

Build against explicit contracts

Capabilities

What the product actually does.

Authentication model

Use server-side, scoped credentials; never expose secrets in browser code.

Planned — contact support

Customer records

Proposed endpoint family for creating and retrieving approved customer data.

Planned — contact support

Invoices and links

Proposed endpoint family for operational billing and collection records.

Planned — contact support

Payment status

Read transaction outcome and associated business context where access is approved.

Planned — contact support

Webhooks

Receive signed events for supported record and payment changes.

Planned — contact support

SDKs

Official language SDK availability is not currently claimed.

Planned — contact support

End-to-end workflow

How the work moves.

01

Request access

Describe the application, required records, data direction, and operating owner.

02

Agree scope

Define credentials, environments, allowed operations, rate expectations, and event handling.

03

Build server-side

Keep secrets out of clients and validate all inputs and webhook signatures.

04

Operate responsibly

Monitor failures, rotate access when required, and update against documented version changes.

Where it fits

Create collection requests

Generate an approved payment or invoice record from an upstream business workflow.

Read account status

Bring approved customer or billing state into another operating surface.

React to events

Use signed event delivery to trigger a controlled downstream process.

Questions

Before you decide.

Is there a public API I can use immediately?

No. API access is currently planned or approved case by case through support.

Can I call it directly from a browser?

Sensitive credentials must remain server-side. Client applications should call their own protected backend.

Scope the right version

Tell us what the workflow needs to accomplish.

Talk to our team