CS2DT Open Platform Access Guide

Update Notes

2026-07-22 Updated the documentation for the Sell and Buy Order functions.
2024-04-30 Initial release. Added the Merchant Center address: https://admin.cs2dt.com

Prerequisites

Before you begin, prepare the following:

• CS2DT account
  Create a CS2DT merchant account through the Merchant Center.
  To use the purchase APIs, you must deposit funds into your account in advance. Check your balance regularly and ensure that you have sufficient funds before submitting a purchase request.
• API key
  All CS2DT API endpoints require an app-key query parameter for authentication.
  You can find your API key under Merchant Center → API Management.
  Keep your API key secure. Do not expose it in client-side code, public repositories, logs, screenshots, or shared request URLs.
  Usage example: https://openapi.cs2dt.com/v1/user/v1/t-coin/balance?app-key=appkey-example

Documentation Overview

The CS2DT Open Platform documentation contains general integration guides, API endpoint references, request and response examples, and data-model definitions.

The following table provides an overview of the main sections.

Section	Description
Response Codes and Errors	Lists API error codes, order failure reasons, and order statuses to help you identify and handle unsuccessful requests or orders.
About Penalties for Reversed Orders / Rollbacks	Explains when penalties may apply after an order or Steam trade is reversed.
About Adjusting the Order Status for Reversed Orders / Rollbacks	Explains how reversed orders should be reported and how their statuses are updated.
Merchant and Steam Accounts	Provides endpoints for checking your account balance and validating a customer’s Steam account and trade information.
Market and Product Search	Provides CS2 or other games item, price, search, filter, and active-listing data.
Purchase Items	Provides endpoints for purchasing a specific product by productId or quickly buying an item by market_hash_name.
Manage Orders	Provides purchase-order history, order details, delayed-order cancellation, and reversed-order reporting.
Callback	Explains how CS2DT sends purchase-order status updates to your configured webhook URL.
Exchange Rate	Provides the USD/CNY exchange rate used by the platform.
WebSocket	Explains how to receive real-time market listing updates and obtain a WSS connection address.
Buy Orders	Provides endpoints for creating, viewing, and cancelling buy orders and checking reference prices.
Sell Your Items	Explains how to list items for sale, manage sell listings, check seller orders, and report order statuses.
Data Models	Defines the request and response objects used by the API endpoints.

Making API Requests

To call a CS2DT API endpoint, send a request using the URL, HTTP method, and parameters specified on that endpoint’s documentation page.

The following sections describe the common request structure:

curl -X GET "https://openapi.cs2dt.com/v1/user/v1/t-coin/balance?app-key=app-key-example"

Base URL

Use the following base URL for API requests:

Availability	Base URL	Description
Global	https://openapi.cs2dt.com	Production OpenAPI base URL

Communication Protocol

All provided API must use HTTPS, providing a highly secure communication channel.

HTTP Methods

Each endpoint uses either GET or POST. Refer to the endpoint documentation for the required method.

Request Parameters

A request may contain two types of parameters:

• Common parameters: Parameters required by multiple or all endpoints. Currently, every request requires the app-key query parameter.

• Endpoint-specific parameters: Parameters required only by a particular endpoint. Refer to the endpoint’s request-parameter table for details.

Depending on the endpoint, parameters may be included in the query string, URL path, or JSON request body.

Character Encoding

Requests and responses use UTF-8 encoding.

Request Signing

Request signing is not currently required. Authenticate each request using your app-key.

Response Format

The API returns a JSON response.
Successful call:

{
    "success": true,
    "data": {
        "userId": 0000000000000000000,
        "name": "usdt_money",
        "data": "0.02"
    },
    "errorCode": 0,
    "errorMsg": null,
    "errorData": null
}

Failed Call:

{
    "success": false,
    "data": null,
    "errorCode": 140020,
    "errorMsg": "请求需要参数app-key",
    "errorData": null
}

Response Fields

Field	Type	Required	Description
success	Boolean	True	Indicates whether the request was processed successfully. If false, check the error fields for details.
errorCode	Integer	True	Error code returned by the API. A successful request normally returns 0; a failed request returns a non-zero value.
errorMsg	String	True	Human-readable error message. It is null or empty when the request succeeds.
data	Object	False	Contains the requested data when the request succeeds. Its structure depends on the endpoint.
errorData	Object	False	Additional information about an error. Its structure depends on the endpoint and error type.
errorCodeStr	String	False	A short English identifier or description for the error. It may be returned when success is false.

Glossary

Term	Description
Service domain name / Base URL	The root URL used for CS2DT API requests. The production base URL is https://openapi.cs2dt.com.
app-key	The credential used to authenticate API requests. Keep it secure and do not share it. Anyone with access to the key may be able to perform operations on your account.
appId	Steam's unique identifier for a game. For example, DOTA2 -> 570, CSGO -> 730, TF2 -> 440, PayDay2->218620, CSOL -> 2504460.

Testing an API Request

How to use the debugging function provided by the interface documentation

You can send test requests directly from the API documentation.

1. Open an API endpoint and click Try it.

2. The first time you test an endpoint, you will be asked to configure the required environment variables. Check how to obtain it in the Prerequisites section.

3. Enter your app-key.

4. After setting, click Send to submit the request and view the response.

Do not use a production API key in screenshots, public demonstrations, or shared environments.