Skip to main content
POST
/
account
/
info
Get account detail
curl --request POST \
  --url 'https://api.flashcat.cloud/account/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "error_code": 0,
  "data": {
    "account_id": 1001,
    "account_name": "acme",
    "domain": "acme",
    "extra_domains": [
      "acme-corp"
    ],
    "phone": "138****8000",
    "country_code": "86",
    "email": "ops@acme.example",
    "avatar": "https://cdn.flashcat.cloud/avatar/acme.png",
    "locale": "zh-CN",
    "time_zone": "Asia/Shanghai",
    "created_at": 1716960000,
    "restrictions": {
      "ips": [
        "203.0.113.0/24"
      ],
      "email_domains": [
        "acme.example"
      ],
      "allow_subdomain": true
    }
  }
}
PermissionDescription
NoneNone — any valid app_key can call this operation.
Find this operation in the Platform API reference.

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

The body is of type object.

Response

OK

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

Endpoint-specific payload. See each operation's 200 response schema.