Activity Status API (Recommended)

The Activity Status API is a key functionality of the TD system aimed at ensuring the accuracy and timeliness of retrieving user identity information.

Through the Activity Status API, we are able to accurately identify more cunning fraudsters who cleverly use normal identities and behaviors to evade detection at critical business checkpoints, thereby deceiving the system. Relying solely on individual business behaviors often proves difficult in revealing the true intentions of fraudsters.

Additionally, the application of the Activity Status API enhances our ability to accurately identify occasional abnormal behaviors of legitimate users, thus reducing false positive rates and improving activity conversion rates. We perform seamless data reporting on users at regular business checkpoints and make decisions at critical business checkpoints. This design helps minimize user interference and enhances user experience.

Through the Activity Status API, we ensure that the TD system consistently receives the latest user identity information, thereby enhancing system security and reliability.

API Format#

Base URL#

• China: https://cn-event.apitd.net/activity/v3
• America: https://us-event.apitd.net/activity/v3
• Singapore: https://sg-event.apitd.net/activity/v3
• Germany: https://de-event.apitd.net/activity/v3

API#

example: https://sg-event.apitd.net/activity/v3?partner_code=test_code&partner_key=test_key

Authentication

Request#

A complete request parameter typically consists of two parts:

1. Basic Parameter: These fields contain fundamental information related to the request itself, aiming to ensure the validity and security of the request.
2. Event Parameter: These fields are related to the activity status, such as marketing, get_coupon, and other events. Through these fields, we can pass data related to specific events, such as marketing information, coupon information, and so on.

By combining the basic fields and event fields, a complete set of request parameters is formed. This design allows us to effectively transmit and process event data related to the activity status, ensuring the accuracy and security of activity information.

Basic Parameter

Event Parameter

Our API design restricts each request to only involve data related to a single event. This means that you cannot simultaneously initiate multiple different event data requests, such as marketing and withdraw.

To ensure data accuracy and system reliability, we recommend that you send separate requests for each event, considering the independence of each event. By handling each event separately, we can better manage and track the data processing process, avoiding confusion and conflicts.

Adhering to this rule will help improve system performance and reliability, ensuring that each event is correctly processed. If you need to handle multiple different events simultaneously, we suggest sending separate requests for each event to ensure data integrity and consistency.

Request Example#

Let's take the example of a get_coupon event.

{
    "channel": "test",
    "session_id": "abc0123456789",
    "account_id": "123456789",
    "event_time": "2021-10-12T14:20:50.521+07:00",
    "event_type": "get_coupon",
    "terminal": {
        "black_box": "aGPH1658920283672ropYaFxT7",
        "ip": "210.20.10.33"
    },
    "ext": {
        "ext_book_id": "LFOUHOFHOHFNOUH",
        "ext_book_num"

Response Parameter#

API Status Code

Response Example#

{
    "code": 200,
    "message": "",
    "sequence_id": "1648777165770866F82AC7F326307055"
}