Skip to main content
REST API Base Endpoint
AvraAPI groups related capabilities into service groups. A provider is the managed implementation that delivers a capability within one of those groups. They are not two separate products: your application calls AvraAPI, while AvraAPI selects the configured provider behind the service.

​
Choose your integration path

SDK integration — Recommended

Use an AvraAPI SDK when one supports the capability you need. SDKs keep credential handling, request creation, and response mapping consistent in your backend.

REST API — Advanced

Use the versioned REST API directly when you need lower-level control or an SDK is not yet available for your language.
Both paths are server-side integrations. Never put a Project Client Secret in browser, mobile, or desktop application code.

​
Service groups and providers

The group pages introduce the available providers. Their reviewed REST operations, request models, responses, errors, and Playground controls are added only after each public contract is verified.

​
What is intentionally outside this reference

This API Reference does not publish payment lifecycle operations, refunds, recurring payments, Workspaces, Wallets, Admin actions, Vault configuration, credential management, webhooks, or account-management actions. Those capabilities use their own protected product flows and are not public Playground operations. Continue with Providers & Microservices to understand the service model, or read the REST API guide for the common request contract.
Last modified on October 1, 2026