# Get Static Web Site File List
Interface should be called on the server side, seeHattori API。
# Interface Dxplaination
# Interface name
getStaticStoreFile
# 初始值
Through this interface can be configured to obtain a list of static website files, such as problems encountered in the course of use, can beOpen Platform Service Provider ZonePosting exchanges.
# Calling mode
# HTTPS call
POST https://api.weixin.qq.com/componenttcb/staticfilelist?access_token=ACCESS_TOKEN
# Request parameters
attribute | type | Required | Introductions |
---|---|---|---|
access_Token | 初始值 | yes | Interface invokes the certificate, which is URL Parameters, non Body Parameters. usecomponent_access_Token |
env | string | yes | Environment ID |
prefix | string | no | Prefix match, which specifies the return file prefix address |
delimiter | string | no | Delimiter as a symbol, if there is Prefix, then the Prefix reach delimiter The same path between are grouped into a class, defined as Common Prefix, and then list all the Common Prefix。 If not, Prefix starts at the beginning of the path |
marker | string | no | Default to UTF-8 List entries in binary order, all listing entries starting with marker |
# Return parameters
attribute | type | Introductions | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
errcode | number | Error code | |||||||||||||||||||||
errmsg | string | Error message | |||||||||||||||||||||
contents | array | File information | |||||||||||||||||||||
| |||||||||||||||||||||||
is_truncated | boolean | Returns whether the content is truncated |
# Call Example
Example Dxplaination: HTTPS requests
# Sample Request Data
{
"env": "test-env1"
}
# Return Data Example
{
"errcode": 0,
"errmsg": "ok",
"contents": [
{
"key": "Dockerfile",
"last_modified": "2020-12-04T08:56:59.000Z",
"md5": "6f58c139dc7aefe41e3b40a8cb8f219-1"
"size": "554"
},
{
"key": " test_export",
"last_modified": "2020-12-04T09:35:56.000Z",
"md5": "e1ab5133bf151a78c466a90fa3a38a6e-1"
"size": "400"
}
],
"is_truncated": false
}
# Error code
Error code | Error code | Solutions |
---|---|---|
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 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 |