Skip to main content
POST
/
calendar
/
info
Get calendar info
curl --request POST \
  --url 'https://api.flashcat.cloud/calendar/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "cal_id": "cal.eh9gvPtWeH3xXgKeVSRxRg"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "account_id": 2451002751131,
    "team_id": 2477033058131,
    "cal_id": "cal.eh9gvPtWeH3xXgKeVSRxRg",
    "cal_name": "Stock Exchange Calendar",
    "description": "A stock market trading calendar example",
    "timezone": "Asia/Shanghai",
    "kind": "personal",
    "workdays": [
      0,
      1,
      2,
      3,
      4,
      5,
      6
    ],
    "created_at": 1702455630,
    "updated_at": 1775529526,
    "creator_id": 2476444212131,
    "updated_by": 3790925372131,
    "status": "enabled"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsNone — any valid app_key can call this operation

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Request body carrying a calendar ID.

cal_id
string
required

Calendar ID.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Service calendar detail.