# Nextiva

> Nextiva is a cloud communications and customer experience company (Scottsdale, AZ) whose NextOS / NEXT platform combines UCaaS business phone service, contact center (NCX), SMS and team messaging, voice AI agents and conversation analytics. Its developer surface is the Nextiva Contact Center platform: five REST OpenAPI 3.0 contracts served from api.nextiva.com and documented at developer.nextiva.com, plus four frontend SDKs (Core, Web, React, React Native) that wrap the same backend over HTTP and two WebSocket channels.

Generated by the API Evangelist enrichment pipeline on 2026-07-31. Not published by Nextiva.
Authentication for every API below: HTTP basic credentials to `generateTokenWithAuthorities` mint a JWT carrying the user's authorities; send it as `Authorization: Bearer <jwt>`; refresh with `refreshToken`. There is no OAuth, no OpenID Connect, no API-key scheme.

## APIs

- [Nextiva Provider Authentication API](https://developer.nextiva.com/nextiva/reference/generatetokenwithauthorities): Login (basic auth to JWT) and token refresh. 2 operations. Base: https://api.nextiva.com
- [Nextiva Provider Token Service API](https://developer.nextiva.com/nextiva/reference/generatetokenwithauthorities): Spring-secured token minting, user authentication redirect, and time-limited multi-tenant portal access tokens. 4 operations. Base: https://api.nextiva.com/provider
- [Nextiva Workitem Service API](https://developer.nextiva.com/nextiva/reference/fetchworkitems): Fetch workitems and control the calls attached to them — bridge, hold, hangup, mute/unmute, DTMF, ACD priority, email response, transfer to agent or inbox. 12 operations. Base: https://api.nextiva.com
- [Nextiva Conversation API](https://developer.nextiva.com/nextiva/reference/fetchconversations): Read the conversation graph — conversations and their workitems, history by participant, campaign- and ticket-scoped conversations, unread counts, activity summaries, transcriptions and recordings. 10 operations. Base: https://api.nextiva.com
- [Nextiva SMS Messaging API](https://developer.nextiva.com/nextiva/reference/sendsmsmessage): Send outbound SMS from a Nextiva user. 1 operation. Base: https://api.nextiva.com

## Specs

- [Provider Authentication OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/openapi/nextiva-authentication-openapi.yml)
- [Provider Token Service OpenAPI 3.0.3](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/openapi/nextiva-provider-authentication-openapi.yml)
- [Workitem Service OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/openapi/nextiva-workitem-service-openapi.yml)
- [Conversation OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/openapi/nextiva-conversation-openapi.yml)
- [SMS Messaging OpenAPI 3.0.0](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/openapi/nextiva-sms-messaging-openapi.yml)

## Docs

- [Developer portal](https://developer.nextiva.com/nextiva/)
- [Overview of SDKs](https://developer.nextiva.com/nextiva/docs/overview-of-sdks)
- [SDK installation](https://developer.nextiva.com/nextiva/docs/sdk-installation)
- [SDK architecture](https://developer.nextiva.com/nextiva/docs/sdk-architecture)
- [Web SDK walkthrough](https://developer.nextiva.com/nextiva/docs/web-sdk-walkthrough)
- [React SDK getting started](https://developer.nextiva.com/nextiva/docs/getting-started-with-the-ncx-react-sdk)
- [React Native SDK walkthrough](https://developer.nextiva.com/nextiva/docs/react-native-sdk-walkthrough)
- [Workitem service](https://developer.nextiva.com/nextiva/docs/workitem-service)
- [Conversation service](https://developer.nextiva.com/nextiva/docs/conversation-service)
- [ACD service](https://developer.nextiva.com/nextiva/docs/acd-service)
- [State service](https://developer.nextiva.com/nextiva/docs/state-service)
- [User service](https://developer.nextiva.com/nextiva/docs/user-service)
- [Call control](https://developer.nextiva.com/nextiva/docs/call-control)
- [Real-time transcription stream](https://developer.nextiva.com/nextiva/docs/real-time-transcription-stream)
- [Schema types overview](https://developer.nextiva.com/nextiva/docs/schema-types-overview)

## Events

Nextiva publishes no AsyncAPI and no customer-configurable HTTP webhooks. Events arrive over two WebSocket channels the SDK opens after login — an events socket (incoming calls, status changes, ACD offers, workitem state changes, live transcription) and an analytics socket (users, queues, campaigns, outbound lists, workitem statistics). Subscribe with `sdk.events$.pipe(ofType(EventTypes.LiveTranscriptionNotification))`.

- [Event catalog](https://raw.githubusercontent.com/api-evangelist/nextiva/refs/heads/main/asyncapi/nextiva-events.yml)

## SDKs

- [ncx-core-sdk (npm)](https://www.npmjs.com/package/ncx-core-sdk)
- [ncx-web-sdk (npm)](https://www.npmjs.com/package/ncx-web-sdk)
- [ncx-react-sdk (npm)](https://www.npmjs.com/package/ncx-react-sdk)
- [ncx-react-native-sdk (npm)](https://www.npmjs.com/package/ncx-react-native-sdk)

Note: the SDK installation guide instructs `npm install @nextiva/ncx-web-sdk` (and the react / react-native equivalents). Those scoped packages return HTTP 404 from the public npm registry as of 2026-07-31 — they are private. The unscoped packages above are the publicly installable builds.

## Company

- [Nextiva](https://www.nextiva.com/)
- [Pricing](https://www.nextiva.com/nextivapricing)
- [Integrations](https://www.nextiva.com/integrations)
- [Help center](https://help.nextiva.com/)
- [Blog](https://www.nextiva.com/blog/)
- [Status page](https://status.nextiva.com/)
- [Security policy and responsible disclosure](https://www.nextiva.com/security-policy.html)
- [Security and privacy certifications](https://www.nextiva.com/resources/learn/security-certification-overview)
- [Legal documents](https://www.nextiva.com/legal.html)
- [Privacy policy](https://www.nextiva.com/privacy-policy.html)
- [GitHub](https://github.com/nextiva)

## Known gaps

- No idempotency contract; the POST call-control operations are not documented as safe to retry.
- No documented rate limits and no 429 response in any contract.
- No request-id / correlation header.
- No API versioning or deprecation policy; no Sunset (RFC 8594) support.
- Errors are a bespoke `{code, message}` (or `{type, message, code, timestamp}`) JSON envelope, not RFC 9457 problem+json, and no error-code registry is published.
- No `/.well-known/` documents on any host; no security.txt despite a real disclosure program.
- No A2A agent card and no MCP server.
- Ten of eleven Workitem Service operations and all ten Conversation operations declare only a `default` error response.