To authenticate your requests, we provide each client a pair of access token and secret
key. The secret key is only used for HMAC SHA-1 signing and not transmitted over the
wire along with your requests.Each request must contain identity authentication
information to confirm the identity and authority of the sender
introduction
Step 1: get token and key
Follow these steps to quickly complete identity authentication
| Test environment | Production environmen | ||||
|---|---|---|---|---|---|
| 1 | Host | http://qa.etowertech.com | Host | http://cn.etowertech.com | |
| 2 | Token | test5AdbzO5OEeOpvgAVXUFE0A | Token | Please contact the integrator | |
| 3 | Key | 79db9e5OEeOpvgAVXUFWSD | Key | Please contact the integrator | |
Step 2: Every request need contain the HTTP header
| Request Headers | ||
|---|---|---|
| X-WallTeach-Date | Request sending time | Time format： RFC1123 Format format：EEE, DD MM YYYY HH:MM:SS ZZZ Sample：Thu, 04 Nov 2021 03:39:28 GMT Notice: Greenwich Mean Time (GMT) is Beijing Time (GMT+8) minus 8 hours. |
| Authorization | The standard HTTP header carries the authentication signature. | Format: WallTech < Token>: <Base64 Encoded HMAC SHA-1 Hash> Sample：WallTech test5AdbzO5OEeOpvgAVXUFE0A:LhpcUyKXCaGcn3tVPwY4nX44XTA= Explain: <Access Token>: API Token |
| Content-Type | application/json | / |
| Accept | application/json | / |