Get Adjacent Three Ledger Dates

Given a ledger date, return the previous, current, and next ledger dates.

Request parameters

Optional: ledger_date (ledger date), format YYYYMMDD; defaults to the current system date when omitted.

Usage notes

The returned ledger_date is the clearing system's current ledger date and may lag the front-office date from get_current_ledgedate. Use it as the ledger date for clearing day-end steps and clearing data changes.

Returns

On success, returns the three adjacent ledger dates. See the response definition below for field meanings.

GEThttps://b-api.lbkrs.com/clearing/get_near_three_ledger_date

Authorization

AuthorizationstringheaderRequired

Send the Broker ACCESS_TOKEN as Authorization: Bearer <token>.

Parameters

ledger_datestring

Ledger date in YYYYMMDD format. When omitted, the current system date is used.

Responses

HTTP 200The request was processed successfully. data contains the three adjacent ledger dates.

Standard response envelopecodemessagedata

dataobjectdata structure

last_ledger_datenumber

Previous ledger date in YYYYMMDD format.

ledger_datenumber

Current ledger date in YYYYMMDD format.

next_ledger_datenumber

Next ledger date in YYYYMMDD format.

availableboolean

Whether the current ledger date is available (boolean).

change_avaliableboolean

Whether the ledger date may be changed (boolean); the field name is spelled change_avaliable exactly as returned by the backend.

HTTP 400Bad request. Check the business error code in code and the error details in message.

Standard response envelopecodemessagedata

dataobjectdata structure

No nested fields

HTTP 401The user is not authenticated, or the login session has expired.

Standard response envelopecodemessagedata

dataobjectdata structure

No nested fields

HTTP 403The current account is not authorized to use this feature. Grant the required permission to the account in User Permission.

Standard response envelopecodemessagedata

dataobjectdata structure

No nested fields

HTTP 408The request timed out. Check the business error code in code and the error details in message.

Standard response envelopecodemessagedata

dataobjectdata structure

No nested fields

Request

curl --request GET \
  --url 'https://b-api.lbkrs.com/clearing/get_near_three_ledger_date' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json'

Response

{
  "code": 0,
  "message": "success",
  "data": {
    "last_ledger_date": 20250101,
    "ledger_date": 20250101,
    "next_ledger_date": 20250101,
    "available": true,
    "change_avaliable": true
  }
}