# Database query record
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
getDatabaseRecord
# Functional description
Through this interface can query the database records. If you encounter problems in the course of use, you canOpen Platform Service Provider ZonePosting exchanges.
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/tcb/databasequery?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 | |||||||||||||||||
pager | object | Paging information | |||||||||||||||||
| |||||||||||||||||||
data | array | Record array |
# Other Notes
Tips Limit should be used in a query()Limit the number of single pull, default 10.
# Call Example
Example Dxplaination: HTTPS requests
# Sample Request Data
{
"env":"test2-4a89da",
"query": "db.collection("geo").where({done:true}).limit(10).skip(1).get()"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"pager": {
"Offset": 1,
"Limit": 10,
"Total": 2
},
"data": [
"{"_id":"B15498AF-1A5A-40B4-A4E7-B3FC4A1DF482","done":true,"name":" test"}"
]
}
# Error code
Error code | Error code | Solutions |
---|---|---|
-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 |
-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 |