Overview

The Voxtelesys Auth API is the OAuth 2.0 authorization server for the Voxtelesys platform. Use it to request the access tokens that authorize requests to Voxtelesys APIs; it also publishes OpenID Connect discovery metadata and the JSON Web Key Set (JWKS) used to verify the JWTs it issues.

OpenAPI Spec

OAuth 2.0

Getting Credentials

OAuth 2.0 setup is managed in the Voxtelesys Portal. You can either use Voxtelesys as your identity provider, or register your own by providing its Discovery URL (ending in /.well-known/openid-configuration).

In the portal, create a client, select the API scopes it needs, and generate a client secret — the resulting client_id and client_secret are the credentials your integration uses at the token endpoint. The Authorization page walks through both setups step by step.

Requesting an Access Token

Request an access token from the Create Token endpoint using the client_credentials grant. Authenticate with HTTP Basic authentication (client_secret_basic), passing your client_id as the username and your client_secret as the password:

curl -X POST https://authapi.voxtelesys.net/api/v1/oauth/token \
  -u "<client_id>:<client_secret>" \
  -d "grant_type=client_credentials"

The response contains the issued access token — a JWT (JSON Web Token) — and its lifetime in seconds:

{
  "access_token": "<token>",
  "token_type": "Bearer",
  "expires_in": 3600
}

Send the access token as a Bearer token in the Authorization header when making requests to protected resources:

Authorization: Bearer <token>

When the token expires, request a new one from the Create Token endpoint.

Discovery

The Auth API publishes its configuration at the standard issuer-root location — https://authapi.voxtelesys.net/.well-known/openid-configuration — not under the /api/v1 base path. The document includes the token endpoint, supported grant types, and the JWKS URI. Services that verify the JWTs issued by the Auth API can retrieve the public signing keys from the JWKS endpoint.

Base URL

All API endpoints are accessible through the following base URL:

https://authapi.voxtelesys.net/api/v1

All requests are served over HTTPS to ensure data privacy. Unencrypted HTTP is not supported.

Regions

The Voxtelesys Auth API is currently supported in the following regions:

Region	ID	Base URL
Salt Lake City	slc	https://authapi.slc.voxtelesys.net/api/v1
Dallas-Fort Worth	dfw	https://authapi.dfw.voxtelesys.net/api/v1
Pittsburgh	pit	https://authapi.pit.voxtelesys.net/api/v1

To send a request to a specific region, use a base URL of the format https://authapi.<region>.voxtelesys.net/api/v1, where <region> is a region ID in the table above. If no region is specified in the base URL, a default region will be automatically selected.

Support

If you encounter any issues or have questions about the API, please reach out to Support. Our team is here to assist you with integration, troubleshooting, and best practices.