https://b-api.longbridge.xyz/clearing/upsert_clearing_ready_settingAuthorization
Send the Broker ACCESS_TOKEN as Authorization: Bearer <token>.
Request body application/json
The corresponding field is read-only on the edit form. Its submitted value comes from
task_code_val on the selected record, not from user input.
On submission, takes the task_code field value (display name) of the current row record, matching the content of the read-only form input.
Processing mode to apply when a pre-clearing check fails.
Values are dynamic. Call GET /v1/datasets/refs/clear_ready_process_mode
to retrieve the current data dictionary, and use the returned entry's key as this field's value.
Allowed values:
0- Tip Only1- Ticket Process2- Forced Calibration
0 · Tip Only1 · Ticket Process2 · Forced Calibration
A switch component; before submission it is converted to a boolean via values.is_enable === true || values.is_enable === 'true'.
A non-business field used only to display the before/after state in the audit log; the front end builds it as {...currentItem, after_enable, before_enable }, containing the two booleans before_enable/after_enable for the enabled state before and after the change.
Responses
HTTP 200The request was processed successfully. The response data does not contain additional business fields.codemessagedatadataobjectdata structureNo nested fields
HTTP 400Bad request. Check the business error code in code and the error details in message.codemessagedatadataobjectdata structureNo nested fields
HTTP 401The user is not authenticated, or the login session has expired.codemessagedatadataobjectdata structureNo nested fields
HTTP 403The current account is not authorized to use this feature. Grant the required permission to the account in User Permission.codemessagedatadataobjectdata structureNo nested fields
HTTP 408The request timed out. Check the business error code in code and the error details in message.codemessagedatadataobjectdata structureNo nested fields