# Database aggregation
<a href="https://developers.weixin.qq.com/初始值 target="_blank" class="api-explorer" > Debugging tools
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
aggregateDatabase
# Functional description
This interface allows database aggregation. If you encounter problems during use, you canOpen Platform Service Provider ZonePosting exchanges
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/tcb/databaseaggregate?access_token=ACCESS_TOKEN
# Third Party Invocation
The calling method and parameters are the same as HTTPS, only the calling token is different
The permission set id to which this interface belongs is: 49, 64
After the service provider has been authorized with one of the permission sets, it can do so by usingauthorizer_access_TokenCalling on behalf of the merchant
# Request parameters
attribute | type | Required | Introductions |
---|---|---|---|
access_Token | string | yes | Interface invokes the certificate, which is URL Parameters, non Body Parameters. useauthorizer_access_Token |
env | string | yes | Cloud Environment ID |
query | string | yes | Database operation statement |
# Return parameters
attribute | type | Introductions |
---|---|---|
errcode | number | Error code |
errmsg | string | Error message |
data | array | Record array |
# Call Example
Example Dxplaination: HTTPS requests
# Sample Request Data
{
"env":"test2-4a89da",
"query": "db.collection(" test_collection").aggregate(). match({tags:"cloud"}).limit(10).end()"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"data": [
"{"_id":f77e039f-f1cf-4aa8-bd59-16cbaa91e6ea","location":{"type":"Point","coordinates":[{"$numberDouble":"113.0"},{"$numberDouble":"23.0"}]},"done":false,"description":"learn cloud database","due":"2019-09-09","tags":["cloud","database"]}",
"{"_id":6bb88938-49ea-42b6-a6f5-ce408970cfc6","due":"2019-09-09","tags":["cloud","database"],"location":{"type":"Point","coordinates":[{"$numberDouble":"113.0"},{"$numberDouble":"23.0"}]},"done":false,"description":" Study cloud database"}",
"{"_id":"51F4F67E-A6A1-4C3E-A50F-827380B8DA86","description":" Study cloud database","due":"2019-09-09","tags":["cloud","database"],"location":{"coordinates":[{"$numberDouble":"113.0"},{"$numberDouble":"23.0"}],"type":"Point"},"done":false}",
"{"_id":"ee1d69da-b7ec-4e7a-bc1f-2fae31da4ce0","tags":["cloud","database"],"location":{"type":"Point","coordinates":[{"$numberDouble":"113.0"},{"$numberDouble":"23.0"}]},"done":false,"description":" Study cloud database","due初始值"2019-09-09"}"
]
}
# Error code
Error code | Error code | Solutions |
---|---|---|
-501000 | ||
-1 | system error | The system is busy, please wait for the developer to try again |
40001 | invalid credential access_Token isinvalid or not latest | Obtain access_Token time AppSecret Error, or access_Token Invalid. Please take the developer more seriously. AppSecret Of the correctness, or to see if you are working for the appropriate Official Account message template Call interface |
0 | ok | ok |
-1000 | system error | System error |
40014 | invalid access_Token | Illegal access_Token Please take the developer seriously. access_Token Of the validity (such as whether it is expired), or to see if you are working for the appropriate Official Account message template Call interface |
40097 | invalid args | Parameter error |
40101 | missing parameter | Missing required parameters |
41001 | access_Token missing | lack access_Token parameter |
42001 | access_Token expired | access_Token Timeout, please check access_Token Of the validity period, please refer to the Basic Support - Obtain access_Token Middle, right. access_Token Detailed mechanism explaination of the |
43002 | require POST method | Need POST request |
44002 | empty post data | POST The packet is empty. |
47001 | data format error | analysis JSON/XML Content errorpost Missing parameters in the dataCheck for corrections and try again. |
85088 | no qbase privilege | The app is not open for cloud development |