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
VZM2MSessionToken apiKey
OAuth2ClientCredentials oauth2
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.