Skip to main content
POST
/
member
/
info
Get current member info
curl --request POST \
  --url 'https://api.flashcat.cloud/member/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "account_avatar": "",
    "account_email": "alice@example.com",
    "account_id": 2451002751131,
    "account_locale": "en-US",
    "account_name": "Acme Corp",
    "account_role_ids": [
      6
    ],
    "account_time_zone": "Asia/Shanghai",
    "avatar": "/image/avatar1.png",
    "country_code": "CN",
    "created_at": 1701399971,
    "domain": "acme",
    "email": "alice@example.com",
    "email_verified": true,
    "is_external": false,
    "locale": "zh-CN",
    "member_id": 2476444212131,
    "member_name": "Alice",
    "phone": "+86185****0300",
    "phone_verified": true,
    "time_zone": "Asia/Shanghai"
  }
}

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

Get member info request

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

Current member profile