> ## 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.

| Page | Package | Status |
| - | - | - |
| [TypeScript HTTP example](https://dialnexa.com/docs/sdks/typescript.md) | No package. Uses `fetch`. | Available today |
| [Python HTTP example](https://dialnexa.com/docs/sdks/python.md) | No package. Uses `requests`. | Available today |
| [React](https://dialnexa.com/docs/sdks/react.md) | `@dialnexa/react` | Planned, not released |
| [React Native](https://dialnexa.com/docs/sdks/react-native.md) | `@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](https://dialnexa.com/docs/api-reference/introduction.md) 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 includes the documented `/v1` operations. For a simple starting point, begin with:

* `POST /v1/calls`: see [Trigger a Call](https://dialnexa.com/docs/api-reference/v1/calls/create.md).

The rest of the API surface is documented in the [API Reference](https://dialnexa.com/docs/api-reference/introduction.md) and reachable through the same authentication model.

## 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 [API fundamentals](https://dialnexa.com/docs/api-reference/api-fundamentals.md#handle-dialnexa-api-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`](https://dialnexa.com/docs/api-reference/openapi.json) so the examples stay consistent with Mintlify's API reference playground.

## Related pages

* [API Introduction](https://dialnexa.com/docs/api-reference/introduction.md): base URLs, authentication, request and response shape.
* [Trigger a Call](https://dialnexa.com/docs/api-reference/v1/calls/create.md): create a single outbound call with the v1 API.
* [API fundamentals](https://dialnexa.com/docs/api-reference/api-fundamentals.md): authentication, error handling, pagination, and retries.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.