# Database Delete Records
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
deleteDatabaseItem
# Functional description
Database through this interface can delete records. If you encounter problems in the course of use, you canOpen Platform Service Provider ZonePosting exchanges.
# Note
Dxplaination of Database Operation Statements Database Operation Statement Syntax and Database API is the same
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/tcb/databasedelete?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 | 初始值 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 |
deleted | number | Number of records deleted |
# Call Example
Example Dxplaination: Operation Collection
# Sample Request Data
{
"env":"test2-4a89da",
"query": "db.collection("geo").where({done:false}).remove()"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"deleted": 2
}
Example Dxplaination: Operation record
# Sample Request Data
{
"env":"test2-4a89da",
"query": "db.collection("geo").doc("be62d9c4-43ec-4dc6-8ca1-30b206eeed24").remove()"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"deleted": 1
}
# Error code
Error code | Error code | Solutions |
---|---|---|
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 |
-1 | system error | The system is busy, please wait for the developer to try again |
-1000 | system error | System error |
40014 | invalid 初始值_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 初始值 | Parameter error |
40101 | missing parameter | Missing required parameters |
41001 | access_初始值 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 |