The Verizon Edge Discovery Service API can direct your application clients to connect to the optimal service endpoints for your Multi-access Edge Computing (MEC) applications for every session. The Edge Discovery Service takes into account the current location of a device, its IP anchor location, current network traffic and other factors to determine which 5G Edge platform a device should connect to.
Verizon Terms of Service: https://www.verizon.com/business/5g-edge-portal/legal.html
If you are building with .NET CLI tools then you can also use the following command:
dotnet add package ThingspacePaymentsSdk --version 1.3.0
You can also view the package at: https://www.nuget.org/packages/ThingspacePaymentsSdk/1.3.0
Note: Documentation for the client can be found here.
The following parameters are configurable for the API Client:
Parameter | Type | Description |
---|---|---|
VZM2mToken |
string |
M2M Session Token (How to generate an M2M session token?) |
Environment |
Environment |
The API environment. Default: Environment.Production |
Timeout |
TimeSpan |
Http client timeout. Default: TimeSpan.FromSeconds(100) |
ClientCredentialsAuth |
ClientCredentialsAuth |
The Credentials Setter for OAuth 2 Client Credentials Grant |
The API client can be initialized as follows:
Verizon.Standard.VerizonClient client = new Verizon.Standard.VerizonClient.Builder()
.ClientCredentialsAuth(
new ClientCredentialsAuthModel.Builder(
"OAuthClientId",
"OAuthClientSecret"
)
.OauthScopes(
new List<OauthScopeEnum>
{
OauthScopeEnum.Discoveryread,
OauthScopeEnum.Serviceprofileread,
})
.Build())
.VZM2mToken("VZ-M2M-Token")
.Environment(Verizon.Standard.Environment.Production)
.Build();
API calls return an ApiResponse
object that includes the following fields:
Field | Description |
---|---|
StatusCode |
Status code of the HTTP response |
Headers |
Headers of the HTTP response as a Hash |
Data |
The deserialized body of the HTTP response as a String |
This API uses the following authentication schemes.
- 5G Edge Platforms
- Service Endpoints
- Service Profiles
- Device Management
- Device Groups
- Session Management
- Connectivity Callbacks
- Account Requests
- Service Plans
- Device Diagnostics
- Device Profile Management
- Device Monitoring
- E UICC Device Profile Management
- Devices Locations
- Devices Location Subscriptions
- Device Location Callbacks
- Usage Trigger Management
- Software Management Subscriptions V1
- Software Management Licenses V1
- Firmware V1
- Software Management Callbacks V1
- Software Management Reports V1
- Software Management Subscriptions V2
- Software Management Licenses V2
- Campaigns V2
- Software Management Callbacks V2
- Software Management Reports V2
- Client Logging
- Server Logging
- Configuration Files
- Software Management Subscriptions V3
- Software Management Licenses V3
- Campaigns V3
- Software Management Reports V3
- Firmware V3
- Account Devices
- Software Management Callbacks V3
- SIM Securefor Io T Licenses
- Account Subscriptions
- Performance Metrics
- Diagnostics Subscriptions
- Diagnostics Observations
- Diagnostics History
- Diagnostics Settings
- Diagnostics Callbacks
- Diagnostics Factory Reset
- Cloud Connector Subscriptions
- Cloud Connector Devices
- Device Service Management
- Device Reports
- Hyper Precise Location Callbacks
- Anomaly Settings
- Anomaly Triggers
- Anomaly Triggers V2
- Wireless Network Performance
- Fixed Wireless Qualification
- Managinge SIM Profiles
- Device SMS Messaging
- Device Actions
- Thing Space Qualityof Service API Actions
- Promotion Period Information
- Retrievethe Triggers
- Update Triggers
- SIM Actions
- Global Reporting
- OAuth Authorization
- Accounts
- SMS
- Exclusions
- Billing
- Targets
- MEC