Verizon · Authentication Profile

Verizon Authentication

Authentication

Verizon ThingSpace uses a two-token model. An OAuth 2.0 client-credentials grant issues a ThingSpace access token from the application key/secret; that token is then exchanged, together with UWS (Unified Web Services) username/password, for a VZ-M2M session token that authorizes every Connectivity Management call. Both tokens must be present on Connectivity Management requests.

Verizon secures its APIs with oauth2 and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

WirelessTelecommunicationsIoT5GEnterpriseNetwork APIsFortune 100
Methods: oauth2, apiKey Schemes: 3 OAuth flows: clientCredentials API key in: header

Security Schemes

ThingSpaceOAuth2 oauth2
· flows: clientCredentials
VZM2MSessionToken apiKey
· in: header ()
OAuth2ClientCredentials oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑
generated: '2026-08-04'
method: searched
source: openapi/verizon-session-api-openapi.yml
docs: https://thingspace.verizon.com/documentation/apis/connectivity-management/getting-started/getting-credentials.html
description: >-
  Verizon ThingSpace uses a two-token model. An OAuth 2.0 client-credentials grant
  issues a ThingSpace access token from the application key/secret; that token is then
  exchanged, together with UWS (Unified Web Services) username/password, for a
  VZ-M2M session token that authorizes every Connectivity Management call. Both
  tokens must be present on Connectivity Management requests.
summary:
  types:
    - oauth2
    - apiKey
  oauth2_flows:
    - clientCredentials
  api_key_in: [header]
schemes:
  - name: ThingSpaceOAuth2
    type: oauth2
    flows:
      - flow: clientCredentials
        tokenUrl: https://thingspace.verizon.com/api/ts/v1/oauth2/token
        scopes: 3
    credential: Application key and secret, colon-joined and Base64-encoded
    request_header: 'Authorization: Basic <base64(key:secret)>'
    response_header: 'Authorization: Bearer <access_token>'
    token_ttl: 3600
    token_ttl_note: >-
      Valid for one hour from first issue; further token requests inside that window
      return the same token rather than minting a new one.
    sources:
      - https://thingspace.verizon.com/documentation/apis/connectivity-management/getting-started/getting-credentials.html
  - name: VZM2MSessionToken
    type: apiKey
    in: header
    parameter_name: VZ-M2M-Token
    obtained_via: openapi/verizon-session-api-openapi.yml#loginSession
    credential: ThingSpace OAuth token + UWS username/password
    token_ttl_note: >-
      Remains valid while the application keeps using it; expires after 20 minutes of
      inactivity. Explicitly terminated with the End Connectivity Management Session
      operation.
    sources:
      - openapi/verizon-session-api-openapi.yml
      - https://thingspace.verizon.com/documentation/apis/connectivity-management/getting-started/getting-credentials.html
  - name: OAuth2ClientCredentials
    type: oauth2
    flows:
      - flow: clientCredentials
        tokenUrl: https://thingspace.verizon.com/api/m2m/v2/session/token
        scopes: 3
    sources:
      - openapi/verizon-accounts-api-openapi.yml
      - openapi/verizon-callbacks-api-openapi.yml
      - openapi/verizon-devices-api-openapi.yml
      - openapi/verizon-session-api-openapi.yml
      - openapi/verizon-sms-api-openapi.yml
    note: >-
      The scheme as declared in the harvested OpenAPI. The docs-confirmed token
      issuer is https://thingspace.verizon.com/api/ts/v1/oauth2/token; the
      /api/m2m/v2 path in the spec is the Connectivity Management base, not the
      token endpoint.
credential_management:
  console: https://thingspace.verizon.com
  path: Account Settings > Key Management > My Keys
combined_request_headers:
  - name: Authorization
    value: Bearer <ThingSpace access token>
    required_on: all requests
  - name: VZ-M2M-Token
    value: <session token>
    required_on: Connectivity Management requests
related:
  scopes: scopes/verizon-scopes.yml
  conventions: conventions/verizon-conventions.yml
  sandbox: sandbox/verizon-sandbox.yml
x-evidence:
  fetched: '2026-08-04'
  urls:
    - https://thingspace.verizon.com/documentation/apis/connectivity-management/getting-started/getting-credentials.html
    - https://thingspace.verizon.com/documentation/apis/connectivity-management/getting-started.html
  http_status: 200

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/verizon-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.