Verizon 5G Edge API Portal
Verizon 5G EdgeThingSpace
HomeSDKsContext PluginAPI Reference
Map message controller

Retrieve SAE J2735 or ETSI MAP messages as a Json list of ASN.1 UPER base64 encoded message with respective region and intersectionIds for the given area.

POST
/api/v2/mapdata/query

This endpoint allows users to download SAE J2735 or ETSI MAP messages as a JSON list. Depending on the expectedType parameter, the response contains either ASN.1 UPER base64-encoded messages with their respective region and intersection IDs, or fully decoded JSON messages. The area for MAP message retrieval must be defined in the request body using one of two methods: An array of region and intersection ID pairs, or a GeoJSON geofence specification.

Authorization

thingspace_oauth sessionToken
AuthorizationBearer <token>

This is the ThingSpace token, from Credentials and Tokens is used

In: header

SessionToken<token>

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

In: header

Header Parameters

VendorID*string

The VendorID set during the Vendor registration call.

Match^[a-zA-Z0-9]+$
Lengthlength <= 64

Request Body

application/json

Request structure for querying MAP records. Provide either regionIntersectionPairs (coordinates) or geoJson, not both.

Query MAP records using specific region and intersection identifier pairs

messageStandard?ETXMessageStandardEnum

V2X messaging standard selection. Accepted values are 'sae' (SAE J2735) and 'etsi' (ETSI TS 103 301).

Match^(etsi|sae)$
Lengthlength <= 4

Value in

  • "etsi"
  • "sae"
regionIntersectionPairs*array<>

List of region and intersection ID pairs to retrieve MAP messages for.

Itemsitems <= 200
expectedType?ETXExpectedTypeEnum

The format of the payload in the response body.

Match^(BASE64|JSON)$
Lengthlength <= 6

Value in

  • "BASE64"
  • "JSON"
pageToken?string

Base64 encoded token used to retrieve the next page of results

Match^[A-Za-z0-9+/]+=*$
Lengthlength <= 500
pageSize?integer

Maximum number of records to return in a single page

Formatint32
Range1 <= value <= 500
Default200

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v2/mapdata/query" \  -H "VendorID: VzMapManager" \  -H "Content-Type: application/json" \  -d '{    "messageStandard": "sae",    "expectedType": "BASE64",    "pageSize": 50,    "regionIntersectionPairs": [      {        "regionId": 100,        "intersectionId": 5233      }    ]  }'
[  {    "messageStandard": "sae",    "regionId": 100,    "intersectionId": 5233,    "payload": "asdfKDSiORel23=="  }]

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

Delete map message DELETE

Removes a map message for the specified region and intersection ID.