Receive General Message
| 第1行： | 第1行： | ||
| − | After connecting with your callback url, Weibo Server will POST the message to your URL when | + | After connecting with your callback url, Weibo Server will POST the general message to your URL when your account get new general messages. |
For each POST request from Weibo, developer can respond it by return specific JSON in response body. | For each POST request from Weibo, developer can respond it by return specific JSON in response body. | ||
Weibo Server will disconnect and request your callback url again if can't receive any response in 5 seconds. Weibo Server will retry 3 times in total. | Weibo Server will disconnect and request your callback url again if can't receive any response in 5 seconds. Weibo Server will retry 3 times in total. | ||
| − | About eliminating the repetitive | + | About eliminating the repetitive messages which may result from the retry mechanism, we recommend you eliminating the repetitive message by using sender_id plus created_at. |
If developer can't respond in 5 seconds, developer can reply with blank string. Weibo Server will not do anything with your blank string and will not retry after receiving your blank string. | If developer can't respond in 5 seconds, developer can reply with blank string. Weibo Server will not do anything with your blank string and will not retry after receiving your blank string. | ||
2014年8月6日 (三) 12:10的版本
After connecting with your callback url, Weibo Server will POST the general message to your URL when your account get new general messages.
For each POST request from Weibo, developer can respond it by return specific JSON in response body. Weibo Server will disconnect and request your callback url again if can't receive any response in 5 seconds. Weibo Server will retry 3 times in total.
About eliminating the repetitive messages which may result from the retry mechanism, we recommend you eliminating the repetitive message by using sender_id plus created_at.
If developer can't respond in 5 seconds, developer can reply with blank string. Weibo Server will not do anything with your blank string and will not retry after receiving your blank string.
目录 |
Text Type Message
The JSON format of Text Type Message as the following：
{
"type": "text",
"receiver_id": 1902538057,
"sender_id": 2489518277,
"created_at": "Mon Jul 16 18:09:20 +0800 2012",
"text": "the content of a general message",
"data": {}
}
| 返回值说明 | ||
|---|---|---|
| Variables | Type | Decription |
| type | string | text |
| receiver_id | int64 | the receiver of this message |
| sender_id | int64 | the sender of this message |
| created_at | string | the creation time of this message |
| text | string | the content of this message |
| data | string | Text Type Message is blank |
Position Type Message
The JSON format of Position Type Message as the following：
{
"type": "position",
"receiver_id": 1902538057,
"sender_id": 2489518277,
"created_at": "Mon Jul 16 18:09:20 +0800 2012",
"text": "我在这里: http://t.cn/zQgLLYO",
"data": {
"longitude": "116.308586",
"latitude": "39.982525"
}
}
| 返回值说明 | ||
|---|---|---|
| Variables | Type | Decription |
| type | string | position |
| receiver_id | int64 | the receiver of this message |
| sender_id | int64 | the sender of this message |
| created_at | string | the creation time of this message |
| text | string | default content about 7 Chinese Characters“发送了一个位置” |
| data | string | the content of this message |
| data:longitude | string | longitude |
| data:latitude | string | latitude |
Voice Type Message
The JSON format of Voice Type Message as the following：
{
"type": "voice",
"receiver_id": 1902538057,
"sender_id": 2489518277,
"created_at": "Mon Jul 16 18:09:20 +0800 2012",
"text": "发了一个语音消息",
"data": {
"vfid": 821804459, // the sender can get the voice file by this ID
"tovfid": 821804469 // the receiver can get the voice file by this ID
}
}
| 返回值说明 | ||
|---|---|---|
| Variables | Type | Description |
| type | string | voice |
| receiver_id | int64 | the receiver of this message |
| sender_id | int64 | the sender of this message |
| created_at | string | the creation time of this message |
| text | string | 私信内容 |
| data | string | 消息内容，纯文本私信或留言为空 |
| data:vfid | string | 语音文件ID，发送者通过此ID读取语音 |
| data:tovfid | string | 语音文件ID，接收者通过此ID读取语音 |
查看（下载）认证用户接收到的语音方法一 curl "https://upload.api.weibo.com/2/mss/msget?access_token=RECIPIENT_ACCESS_TOKEN&fid=TOVFID" 1."RECIPIENT_ACCESS_TOKEN"：返回结果中接收者（recipient_id）通过OAuth2授权返回的access_token； 2."TOVFID"：返回结果data字段中的tovfid。 查看（下载）认证用户接收到的语音方法二 curl -u "USERNAME:PASSWORD" "https://upload.api.weibo.com/2/mss/msget?source=APPKEY&fid=TOVFID" 1."USERNAME:PASSWORD"为"recipient_id"（认证用户）的微博登录用户名和密码，此时方法二中的APPKEY应用所有者为"recipient_id"； 2."TOVFID"：返回结果data字段中的tovfid。
Image Type Message
The JSON format of Image Type Message as the following：
{
"type": "image",
"receiver_id": 1902538057,
"sender_id": 2489518277,
"created_at": "Mon Jul 16 18:09:20 +0800 2012",
"text": "发了一张图片",
"data": {
"vfid": 821804459, // 发送者用此ID查看图片
"tovfid": 821804469 // 接收者用此ID查看图片
}
}
| 返回值说明 | ||
|---|---|---|
| Variables | Type | Description |
| type | string | image |
| receiver_id | int64 | the receiver of this message |
| sender_id | int64 | the sender of this message |
| created_at | string | the creation time of this message |
| text | string | 私信内容 |
| data | string | 消息内容，纯文本私信或留言为空 |
| data:vfid | string | 图片ID，发送者通过此ID读取图片 |
| data:tovfid | string | 图片ID，接收者通过此ID读取图片 |
查看（下载）图片 curl "https://upload.api.weibo.com/2/mss/msget?access_token=RECIPIENT_ACCESS_TOKEN&fid=TOVFID" 1，"RECIPIENT_ACCESS_TOKEN"：返回结果中接收者（receiver_id）通过OAuth2授权返回的access_token； 2，"TOVFID"：返回结果data字段中的tovfid。
