How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nextiva Authentication API

User login and token management operations.

Nextiva Authentication API is one of 10 APIs that Nextiva publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 4 base URLs: https://api.nextiva.com, https://api.nextiva.com/provider, https://api-staging.nextiva.com/provider, http://localhost:8080.

6 operations 6 paths 6 schemas 5 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.nextiva.com
Authentication
HTTP Basic, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Nextiva Authentication API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP bearer tokens (JWT) (springAuth).

  • basicAuth — Basic authentication using username and password.
  • bearerAuth — Bearer token authentication (JWT).
  • springAuth — Spring Security authentication using JWT tokens. All endpoints require an authenticated user context.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 5 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication 6

User login and token management operations.

GET
/provider/token-with-authorities
Generate token with user authorities (Login)
generateTokenWithAuthorities → 200401default
GET
/provider/api/token-refresh
Refresh authentication token
refreshToken → 200401default
GET
/token-with-authorities
Generate token with user authorities (test)
generateTokenWithAuthorities → 200401403500
GET
/token
Generate basic token
generateToken → 200401403500
POST
/auth
Authenticate and redirect
authenticate → 302401403500
GET
/portal/token-with-authorities
Generate portal access token
generatePortalToken → 200400401403500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (4 properties), TokenAuthenticationResponse (3 properties), TokenResponse_2 (3 properties), RefreshTokenResponse (3 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
TokenResponse
object
2 properties 2 required
RefreshTokenResponse
object
3 properties 3 required
TokenResponse_2
object
Extended response with token expiration information
3 properties 3 required
TokenAuthenticationResponse
object
Response containing JWT token and location information
3 properties 2 required
ErrorResponse
object
Standardized error response
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nextiva-authentication-api-openapi.yml Raw ↑

Other APIs Nextiva publishes across the network.

Nextiva Call Management API
Nextiva Campaigns API
Nextiva Conversations API
Nextiva DTMF API
Nextiva Email API
Nextiva SMS Messaging API
Nextiva Tickets API
Nextiva Transfers API
Nextiva Workitems API
Where this information came from

This is an independent, third-party profile of Nextiva Authentication API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.