Send a list of SDII messages to a stream layer

post

https://use.apilookup.for.a.base.url/layers/{layerId}/sdiiMessageList

Consumes individual SDII messages and SDII MessageLists. The endpoint automatically breaks SDII MessageLists down and stores the data as individual SDII messages. Note that this endpoint does not support compression. If you are sending data to stream layer that has compression enabled, you must use the /layers/<layerID> endpoint and all compression and decompression must be handled by your application.

Path Params

layerId

string

required

The ID of the layer where you want the data ingested.

Query Params

billingTag

string

Optional billing tag provided by customer. It will be used in grouping of billing records.

Body Params

A byte array of data in SDII MessageList protobuf format to send to the HERE platform for ingestion. The maximum size is 20 MB. Decode the example from base64 before using.

Headers

X-HERE-Checksum

string

A base64 encoded SHA-256 hash you can provide for validation against the calculated value on the request body hash. This verifies the integrity of your request and prevents modification by a third party.It will be created by the service if not provided. A SHA-256 hash consists of 256 bits or 64 chars.

X-HERE-TraceId

string

A unique message ID, such as a UUID. This can be included in the request if you want to use an ID that you define. If you do not include an ID, one will be generated during ingestion and included in the response. You can use this ID to track your request and identify the message in the catalog.

X-HERE-Message-Key

string

A unique message ID, such as a UUID. This can be included in the request if you want to use an ID that you define. If you do not include an ID, X-HERE-TraceId will be used instead. You can use this ID to specify the partition for the message in the data catalog.

Responses

401

Unauthorized

200OK

400Bad Request

404No handler found

413Payload Too Large

415Unsupported Media Type

500Internal Server Error