Authentication
Echo test
Validates the whole signing pipeline and returns the identity of the calling application.
POST
/openapi/demo/echoRequires the
token, timestamp and sign signature headers, see Authentication.Recommended as the first call of every integration: when the signature is correct, the response echoes the message you sent together with the application appKey. Unlike the standard endpoints, echo responds with the platform envelope (success / data).
Headers
Content-Type* | string | Content-Type |
* Required field
Request body
message* | string | Message |
* Required field
200
Signature accepted. Platform envelope with the echoed message and the application identity.
success | bool | Call outcome |
message | string | Result text |
| object | Response payload |
Make one call with a JSON body and one GET call to any standard endpoint with an empty body before moving on: the two cases cover both signing rules, body without CR/LF and empty body. The platform also offers a sign helper in the console: give it the path and the exact body and it returns the expected token / timestamp / sign plus a ready-to-run curl command.
| Code | HTTP | |
|---|---|---|
| 10009000 | 401 | Missing signature headers (token / timestamp / sign). |
| 10009001 | 401 | Timestamp invalid or outside the ±300 s window. |
| 10009002 | 401 | Invalid token. |
| 10009003 | 401 | Signature mismatch. See the troubleshooting section under Authentication. |
| 10009005 | 403 | Application not subscribed to the /openapi/demo/echo scope. |