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 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
Keep API credentials on the server
Store the DialNexa API key in a server environment variable. Never include it in a browser bundle.
Create server-side routes
Use a server route, server action, or backend service for authenticated DialNexa API requests. The TypeScript HTTP example shows the supported request pattern.
Use the current web call surface
Follow Web Calls for the browser call experience available today.
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 for the current browser voice experience.
- TypeScript HTTP Example for secure server-side requests.
- API Authentication for API key requirements.
- Call History for verifying calls.