API Overview

API Overview

The same API used by Subphonic Transact is available for your own integrations. You can use it to create sessions, manage capture flows, and submit payments from your application stack.

The same API surface supports DTMF, voice capture, and digital channel journeys, so you only need one integration model.

Live API Documentation

For full endpoint reference, request/response schemas, and implementation examples, use the live Transact API docs:

• Transact API Documentation
• Transact API Documentation (workspace route)

Authentication Model

Transact APIs use JWT-based authentication:

1. A long-lived service JWT is issued for your account and managed in the Transact portal.
2. Your integration calls the Transact Auth service to generate short-lived application JWTs.
3. These short-lived tokens are used when calling operational API endpoints.

This model helps reduce risk by limiting token lifetime while keeping server-to-server integration straightforward.

When To Use The API Directly

Use direct API integration when you need to:

• Embed Transact into your own IVR, CRM, or backend orchestration flow.
• Control payment/capture lifecycle from your own services.
• Integrate completion outcomes into internal workflows and reporting.

For implementation details, continue to the full API reference linked above.