English
Deprecate Preset Object
About 180 wordsLess than 1 minute
2026-01-19
Not recommended to continue using deprecated APIs!!!
Description
Deprecate a preset object.
Request Specification
HTTP Method: POST + application/json
Request Path: https://${cloud-domain}/cgi/crm/v2/data/invalid?thirdTraceId=${Random String}
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| corpAccessToken | String | Yes | corpAccessToken (returned via Get Token API) |
| corpId | String | Yes | corpId (returned via Get Token API) |
| currentOpenUserId | String | Yes | currentOpenUserId (returned via Query Employee by Mobile API) |
| data | Map | Yes | Data map |
| object_data_id | String | Yes | List of data IDs |
| dataObjectApiName | String | Yes | Object API name |
Request Example
{
"corpAccessToken": "{corpAccessToken}",
"currentOpenUserId": "{currentOpenUserId}",
"corpId": "{corpId}",
"data": {
"object_data_id": "hello",
"dataObjectApiName": "CampaignMembersObj"
}
}Response Parameters
| Parameter | Type | Description |
|---|---|---|
| traceId | string | Unique request ID |
| errorDescription | string | Error description |
| errorMessage | string | Error message |
| errorCode | Int | Error Codes |
Response Example
{
"traceId": "E-O.827xxxxxx",
"errorDescription": "success",
"errorMessage": "OK",
"errorCode": 0
}Notes
- Do not use the message field in the response for logical judgments, as errorMessage may change;
