> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa Code Examples And SDK Status

> Call the DialNexa API from Python or TypeScript today and check the current status of planned web and mobile SDKs.

DialNexa provides a REST API that you can call from any server-side language. Python and TypeScript pages show supported HTTP patterns available today. First-party React and React Native packages are not currently released.

<Note>
  **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.
</Note>

| Page                                        | Package                      | Status                |
| ------------------------------------------- | ---------------------------- | --------------------- |
| [TypeScript HTTP example](/docs/sdks/typescript) | No package. Uses `fetch`.    | Available today       |
| [Python HTTP example](/docs/sdks/python)         | No package. Uses `requests`. | Available today       |
| [React](/docs/sdks/react)                        | `@dialnexa/react`            | Planned, not released |
| [React Native](/docs/sdks/react-native)          | `@dialnexa/react-native`     | Planned, not released |

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](/docs/api-reference/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](/docs/api-reference/v1/calls/create).

The rest of the API surface is documented in the [API Reference](/docs/api-reference/introduction) and reachable through the same authentication model. Prefer `/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:

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](/docs/api-reference/errors)) without hiding them.

The language-specific pages in this section show this pattern with concrete examples.

<Note>
  This section is intentionally aligned with [`/api-reference/openapi.json`](/docs/api-reference/openapi.json) so the examples stay consistent with Mintlify's API reference playground.
</Note>

## Related pages

* [API Introduction](/docs/api-reference/introduction): base URLs, authentication, request and response shape.
* [Trigger a Call](/docs/api-reference/v1/calls/create): create a single outbound call with the v1 API.
* [Errors](/docs/api-reference/errors): error format and codes returned by every endpoint.
* [Authentication](/docs/api-reference/authentication): how API keys are sent and verified.