Getting Started with Verizon
Introduction
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
Install the Package
The package is compatible with Python versions 3 >=3.7, <= 3.11.
Install the package from PyPi using the following pip command:
pip install thingspace-payments-sdk-sdk==1.3.0
You can also view the package at: https://pypi.python.org/pypi/thingspace-payments-sdk-sdk/1.3.0
Initialize the API Client
Note: Documentation for the client can be found here.
The following parameters are configurable for the API Client:
| Parameter | Type | Description |
|---|---|---|
vz_m2m_token |
str |
M2M Session Token (How to generate an M2M session token?) |
environment |
Environment |
The API environment. Default: Environment.PRODUCTION |
http_client_instance |
HttpClient |
The Http Client passed from the sdk user for making requests |
override_http_client_configuration |
bool |
The value which determines to override properties of the passed Http Client from the sdk user |
http_call_back |
HttpCallBack |
The callback value that is invoked before and after an HTTP call is made to an endpoint |
timeout |
float |
The value to use for connection timeout. Default: 60 |
max_retries |
int |
The number of times to retry an endpoint call if it fails. Default: 0 |
backoff_factor |
float |
A backoff factor to apply between attempts after the second try. Default: 2 |
retry_statuses |
Array of int |
The http statuses on which retry is to be done. Default: [408, 413, 429, 500, 502, 503, 504, 521, 522, 524] |
retry_methods |
Array of string |
The http methods on which retry is to be done. Default: ['GET', 'PUT'] |
client_credentials_auth_credentials |
ClientCredentialsAuthCredentials |
The credential object for OAuth 2 Client Credentials Grant |
The API client can be initialized as follows:
client = VerizonClient(
vz_m2m_token='VZ-M2M-Token',
client_credentials_auth_credentials=ClientCredentialsAuthCredentials(
oauth_client_id='OAuthClientId',
oauth_client_secret='OAuthClientSecret',
oauth_scopes=[
OauthScopeEnum.DISCOVERYREAD,
OauthScopeEnum.SERVICEPROFILEREAD
]
)
)
API calls return an ApiResponse object that includes the following fields:
| Field | Description |
|---|---|
status_code |
Status code of the HTTP response |
reason_phrase |
Reason phrase of the HTTP response |
headers |
Headers of the HTTP response as a dictionary |
text |
The body of the HTTP response as a string |
request |
HTTP request info |
errors |
Errors, if they exist |
body |
The deserialized body of the HTTP response |
Authorization
This API uses the following authentication schemes.
List of APIs
- 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
Classes Documentation
Metadata
Release files for thingspace-payments-sdk-sdk 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| thingspace-payments-sdk-sdk-1.3.0.tar.gz | 217.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| thingspace_payments_sdk_sdk-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 917.0 kB
Release files / thingspace-payments-sdk-sdk-1.3.0.tar.gz
| Download URL | thingspace-payments-sdk-sdk-1.3.0.tar.gz |
|---|---|
| Size | 217.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d7171a689081c0120465a5ec36652928ecb6ba96fed6db7501d85140f3d5f59
|
|
BLAKE2b-256 checksum How to use checksums |
78db5515dc4f5da22358e9c9b02b3db10ede54cf0909d4ffe83073fab2ce2ff9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Release files / thingspace_payments_sdk_sdk-1.3.0-py3-none-any.whl
| Download URL | thingspace_payments_sdk_sdk-1.3.0-py3-none-any.whl |
|---|---|
| Size | 699.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5029cde2b4a18d63f303c45ea02e88a7e6ec5e9d3e739593c7356b6588040ca
|
|
BLAKE2b-256 checksum How to use checksums |
d2b4e4ef22cef2d57d2384b4d4ffacf630e7a1fa44160c2845b4dde5cd531bad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Security for thingspace-payments-sdk-sdk 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.