Callback Authentication Method

In order to provide more secure authentication for callback requests, we recommend using additional authentication methods for security verification.

Callback Authentication Instructions

Get callback_token and callbakc_secret through the dashboard

To ensure callback security, the platform appends the following parameters to the request header of each request

You can do simple verification directly by verifying that Callback-Token is consistent, More secure authentication is also possible with Signature

Param	Description	Example
Callback-Token	Callback Token from Callback Authentication page	EEB0C8EEB1B6C7D9C7D938449C44DAE7DC484C87C14E
Date	Current timestamp in ISO-8601 format	2024-06-17T00:00:00Z
Signature	Base64-encoded signature information (calculated using a hash algorithm).	Please refer to the following Signature for the rule of generating.

Signature Specifies the rule for generating

Name	Description	Example
Date	Current timestamp in ISO-8601 format	2024-06-17T00:00:00Z
callback_url	The full callback URL, including the protocol and parameters	`https://api.you.com/callback?id=32`

Generating the Signature parameter involves these steps:

Construct signature_origin:

signature_origin is formed by concatenating the following parameters using | as the delimiter:{date} | {callback_url}

Example: `2024-06-17T00:00:00Z | https://api.you.com/callback?id=32`

Generate signature_sha:

Calculate signature_sha using HMAC-SHA256 with callbakc_secret:

signature_sha=hmac-sha256(signature_origin, callbakc_secret)

Encode signature_sha:

Encode signature_sha using base64 to obtain the final signature:

`signature=base64(signature_sha)`

This yields the signature parameter.

Callback Authentication Method

Callback Authentication Instructions#

Signature Specifies the rule for generating#

Callback Authentication Instructions

Signature Specifies the rule for generating