Retrieve devices by vendor and optional filters
This API allows retrieving devices by vendor ID and optional filters. The request should include the VendorID and any filters to apply.
Authorization
thingspace_oauth sessionToken This is the ThingSpace token, from Credentials and Tokens is used
In: header
This is the Session/M2M token needed to authenticate the user. It should be acquired by using the ThingSpace APIs. For detail on how to obtain a Session/M2M token please refer to the
- ThingSpace Quick Start Guide - Obtaining a VZ-M2M Session Token Programmatically
- or the ThingSpace API Video Guide 1 and ThingSpace API Video Guide 2
In: header
Header Parameters
Optional transaction identifier for tracing requests. If not provided, the application will generate one.
uuidRequest Body
application/json
Request body for retrieving devices based on vendorID and optional filters
The ID the vendor wants its devices to be registered under. E.g. Verizon, GM, Ford, etc.
^[a-zA-Z0-9]+$length <= 64Devices filter criteria or pagination token
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/v1/clients/query" \ -H "Content-Type: application/json" \ -d '{ "VendorId": "VerizonETX" }'[]Retrieve MQTT URL for device or software service connection to the Message Exchange with muti-MECs support POST
With this API call the device or software service requests the MQTT URL for the location that it needs to connect. To determine the proper URL the device or software service needs to provide its ID (the one that was provided in the registration request), location (GPS coordinates), and whether it is on the Verizon cellular network or not. If there are multiple MECs that serve the location of the client all options are provided in the response, and the client is free to choose which MEC they want to connect. Note: The user needs to authenticate with their ThingSpace credentials using the Access/Bearer and Session/M2M tokens in order to call this API.
Download SAE J2735 or ETSI MAP messages in ASN.1 UPER base64 encoded format for the given area. GET
This endpoint is deprecated. (Use /api/v2/mapdata/query for new integrations). This endpoint allows user to download SAE J2735 or ETSI MAP messages in ASN.1 UPER base64 encoded format. The area for the MAP messages is needed to be defined in the query. **Required request header:** `Accept` — specifies the response format. Omitting this header will result in a `400 Bad Request`. Supported values: - `text/plain` — ASN.1 UPER base64-encoded MAP messages (one per line) - `application/json` — JSON-encoded MAP messages