Convirza V3 uses a distributed microservices architecture with separate OAuth and business logic services.Backend Services#
| Service | Base URL (Production) | Purpose |
|---|
| OAuth | https://platform-oauth.convirza.com | Authentication — login, refresh, revoke |
| Public APIs | https://platform-api.convirza.com/v3 | All business logic endpoints |
Token Architecture#
Convirza uses encrypted session tokens:1.
Call POST /oauth/token with your credentials to receive an encrypted access_token and refresh_token
2.
Tokens are opaque identifiers that cannot be decoded client-side — always use them as-is
3.
Include the token in the Authorization: Bearer <token> header on every API request
4.
Revoke tokens immediately by calling POST /oauth/revoke-token
Authentication Endpoints#
| Endpoint | Method | Description |
|---|
/oauth/token | POST | Login — returns access_token + refresh_token |
/oauth/refresh-token | POST | Exchange refresh token for new access token |
/oauth/revoke-token | POST | Revoke a token immediately |
API Structure#
All business logic endpoints are under https://platform-api.convirza.com/v3:/v3/
├── auth/profile — Authenticated user profile
├── users/ — User management
├── groups/ — Organization hierarchy
├── webhooks/ — Event subscriptions
├── media-prompts/ — Audio file uploads
├── ai-voice-agents/ — AI voice agent management
├── broadcast/ — SMS broadcast campaigns
├── phone-numbers/ — Number search, order, release
├── conversations/
│ ├── calls — Call history and transcriptions
│ └── sms — SMS conversation threads
├── provisioned-routes/ — Call routing rules
├── industry — Industry reference list
├── ad-source — Ad source reference list
└── tag/ — Tag management
Modified at 2026-04-13 06:15:41