No first-party SDK packages are available today. Use the HTTP API for production integrations. Planned SDK pages describe status only and do not define a public interface.
The HTTP examples are designed so you can paste them into your codebase, replace the placeholder API key, and have a working integration in minutes.
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.
Use DialNexa Code Examples Today
The published OpenAPI document now includes the documented/v1 operations and the legacy operations that remain available during the migration period. For a simple starting point, begin with:
POST /v1/calls: see Trigger a Call.
/v1 endpoint pages for new integrations.
Build A Thin HTTP Wrapper
Until first-party SDKs ship, the recommended pattern is a thin per-service wrapper in your own codebase that:- Centralizes the base URL, default headers, and authentication.
- Maps each endpoint to a typed function in your language of choice.
- Surfaces DialNexa error responses (see Errors) without hiding them.
This section is intentionally aligned with
/api-reference/openapi.json so the examples stay consistent with Mintlify’s API reference playground.Related pages
- API Introduction: base URLs, authentication, request and response shape.
- Trigger a Call: create a single outbound call with the v1 API.
- Errors: error format and codes returned by every endpoint.
- Authentication: how API keys are sent and verified.