> ## 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 React SDK Status

> Check the status of the planned DialNexa React SDK and use supported web calls and server-side API requests today.

The DialNexa React SDK is planned but not released. There is no supported React package to install, and the public component, hook, event, and authentication interfaces have not been finalized.

## Current DialNexa React SDK Status

| Question                                         | Current answer                                                            |
| ------------------------------------------------ | ------------------------------------------------------------------------- |
| Can I install a DialNexa React package?          | No. No first-party React package is published.                            |
| Is the public React API finalized?               | No. Do not build against proposed package names or interfaces.            |
| Can I add a voice experience to a website today? | Use the supported [Web Calls](/docs/calls/web-calls) path.                     |
| Can my React application call the REST API?      | Yes, from a secure server or server-side route that protects the API key. |

## Use DialNexa In A React Application Today

<Steps>
  <Step title="Keep API credentials on the server">
    Store the DialNexa API key in a server environment variable. Never include it in a browser bundle.
  </Step>

  <Step title="Create server-side routes">
    Use a server route, server action, or backend service for authenticated DialNexa API requests. The [TypeScript HTTP example](/docs/sdks/typescript) shows the supported request pattern.
  </Step>

  <Step title="Use the current web call surface">
    Follow [Web Calls](/docs/calls/web-calls) for the browser call experience available today.
  </Step>

  <Step title="Verify call evidence">
    Confirm created calls in Call History and review their status, transcript, recording, and end reason.
  </Step>
</Steps>

## Avoid Planning Against An Unreleased Interface

Do not commit production code to an assumed package name, React hook, callback, token format, or browser transport. Those details can change before a public SDK exists.

## Related Pages

* [Web Calls](/docs/calls/web-calls) for the current browser voice experience.
* [TypeScript HTTP Example](/docs/sdks/typescript) for secure server-side requests.
* [API Authentication](/docs/api-reference/authentication) for API key requirements.
* [Call History](/docs/monitoring/call-history) for verifying calls.