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

Upload SAE J2735 MAP messages in ASN.1 UPER or JER (JSON) base64 encoded format format.

POST
/api/v2/mapdata

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

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
MapDataMessageStandard*ETXMessageStandardEnum

Select which V2X messaging standard will be used for the message generation. The following options are supported:

  • "etsi": The message will be generated using the ETSI (European) standard (e.g. MAPEM).
  • "sae": The message will be generated using the SAE J2735 (North American) standard (e.g. MAP).
  • if not sent while POST, defaults to "sae"
Match^(etsi|sae)$
Lengthlength <= 4

Value in

  • "etsi"
  • "sae"

Request Body

application/json

UPER/ASN.1 J2735/ETSI base64 encoded MapData message or JSON representation of the MapData message.

UPER/ASN.1 J2735/ETSI base64 encoded MapData message or JSON representation of the MapData message.

messageId*integer

SAE J2735 DSRCmsgID for the MAP message type.

Formatint32
Range0 <= value <= 32767
value*

The decoded MAP message body containing intersection and lane data.

msgIssueRevision?integer

Issue revision number of the MAP message.

Formatint32
Range0 <= value <= 255

Response Body

text/plain

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v2/mapdata" \  -H "VendorID: VzMapManager" \  -H "MapDataMessageStandard: sae" \  -H "Content-Type: application/json" \  -d '{    "messageId": 18,    "value": {      "intersections": [        {          "id": {            "region": 0,            "id": 156          },          "laneWidth": 366,          "refPoint": {            "lat": 389284111,            "long": -772410713          },          "revision": 3        }      ],      "msgIssueRevision": 3    }  }'
"string"

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

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

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.