Authentication
Echo test
Validates the whole signing pipeline and returns the identity of the calling application.
/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).
Parameters
Headers
Content-TypestringrequiredAlways
application/json.
Request body
messagestringrequiredAny text up to 512 characters; returned unchanged in
data.echo.Example:hello tffiscal
Responses
Signature accepted. Platform envelope with the echoed message and the application identity.
successbooleanOutcome of the call.
messagestringOKon success.dataobjectResponse payload.
Errors
| Code | HTTP | |
|---|---|---|
| 10009000 | 401 | Missing signature headers ( |
| 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 |
How to use it during integration
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.