Get message metadata
Retrieve the metadata (key-value pairs) for a specified message by its message UID.
Request method
POST: https://Base URL/v4/community-channel/message/metadata/list
Rate limit: 100 requests per second
Signature required: All server API requests require signature verification. See API request signature.
Request body
The request body is in application/json format and supports the following parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
messageUID | String | Yes | The message UID. Obtainable via the message routing service. See Message routing. |
channelId | String | Yes | The community channel ID. |
subchannelId | String | No | The subchannel ID. Required if the message was sent with a subchannel ID; must be omitted if the message was sent without one. On the client side, this corresponds to channelId. |
page | Number | No | Page number. Defaults to returning up to 300 metadata entries. |
Request example
HTTP
POST /v4/community-channel/message/metadata/list HTTP/1.1
Host: api.sg-light-api.com
App-Key: uwd1c0sxdlx2
Nonce: 14314
Timestamp: 1585127132438
Signature: 890b422b75c1c5cb706e4f7921df1d94e69c17f4
Content-Type: application/json
{
"messageUID": "BRGM-DEN2-01E4-BN66",
"channelId": "WNYZbMqpH",
"subchannelId": "abc",
"page": 1
}
Response
The response body contains a JSON object with the following structure:
| Field | Type | Description |
|---|---|---|
code | Number | Status code. 0 indicates success. |
result.metadata | Object | Message metadata as key-value pairs. Key: max 32 characters, supports letters, numbers, and + = - _ (no Chinese characters). Value: max 4096 characters. |
Response example
HTTP
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{
"code": 0,
"result": {
"metadata": {
"status": {
"value": "delivered",
"updatedAt": 1742457600000
}
}
}
}