Download SAE J2735 or ETSI MAP messages in ASN.1 UPER base64 encoded format for the given area.
Deprecated
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
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
Query Parameters
GeoJSON Polygon defining the area to retrieve MAP messages for.
Header Parameters
The VendorID set during the Vendor registration call.
^[a-zA-Z0-9]+$length <= 64Response Body
text/plain
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v2/mapdata?type=Polygon&coordinates=-77.479395%2C38.990773%2C-77.114566%2C38.99944%2C-77.100228%2C38.817204%2C-77.418059%2C38.827754%2C-77.479395%2C38.990773" \ -H "VendorID: VzMapManager""string"Retrieve devices by vendor and optional filters POST
This API allows retrieving devices by vendor ID and optional filters. The request should include the VendorID and any filters to apply.
Upload SAE J2735 MAP messages in ASN.1 UPER or JER (JSON) base64 encoded format format. POST
This endpoint allows the user to upload map messages in ASN.1 UPER base64 encoded format or JER (JSON) formats. The MAP data message can have more than one intersections in it. Both SAE and ETSI defined MAP messages are supported. The SAE type MAP messages have to be wrapped in a MessageFrame, as defined in the SAE J2735 standard. The ETSI type MAP messages are expected as MAPEM structures that include the ETSI header, as defined in the ETSI TS 103 301 standard. Note: The user needs to authenticate with their ThingSpace credentials using the Access/Bearer and Session/M2M tokens in order to call this API. **Required request header:** `Content-Type` — specifies the format of the request body. Omitting or sending an unsupported value will result in a `415 Unsupported Media Type`. Supported values: - `text/plain` — ASN.1 UPER base64-encoded MAP message - `application/json` — JSON representation of the MAP message