Skip to main content
DialNexa is a REST API that can be called directly from any server-side language. Until first-party SDK packages are published, you can use standard HTTP clients in any language, and the language-specific pages in this section give copy-paste examples that map one-to-one with the current OpenAPI spec. The examples are designed so you can paste them into your codebase, replace the placeholder API key, and have a working integration in minutes.

​
What is in this section

  • Python: HTTPX and requests examples for triggering calls and handling webhooks.
  • TypeScript: Node-friendly fetch examples for server-side use.
  • React and React Native: client-side patterns for browser and mobile.
If you are evaluating which surface to use, start at the API Introduction for the request/response format, base URLs, and authentication model. Every endpoint in the reference includes a built-in playground for quick testing.

​
Current OpenAPI coverage

The published OpenAPI document currently includes one operation: The rest of the API surface (agents, workflows, campaigns, webhooks, phone numbers, voices, languages, transcribers, batches, and call logs) is documented in the API Reference and reachable through the same authentication model. The OpenAPI spec is expanding in upcoming releases; watch the Changelog for updates.

​
Pattern: thin HTTP wrappers

Until first-party SDKs ship, the recommended pattern is a thin per-service wrapper in your own codebase that:
  1. Centralizes the base URL, default headers, and authentication.
  2. Maps each endpoint to a typed function in your language of choice.
  3. Surfaces DialNexa error responses (see Errors) without hiding them.
The language-specific pages in this section show this pattern with concrete examples.
This section is intentionally aligned with /api-reference/openapi.json so the examples stay consistent with Mintlify’s API reference playground.
  • API Introduction: base URLs, authentication, request and response shape.
  • Trigger a Call: the first operation covered in the OpenAPI spec.
  • Errors: error format and codes returned by every endpoint.
  • Authentication: how API keys are sent and verified.