Skip to main content
POST
/
team
/
info
Get team detail
curl --request POST \
  --url 'https://api.flashcat.cloud/team/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "team_id": 1001
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "account_id": 10023,
    "team_id": 1001,
    "team_name": "Backend SRE",
    "description": "Backend reliability engineering team",
    "status": "enabled",
    "updated_by_name": "alice",
    "updated_by": 80011,
    "creator_id": 80011,
    "creator_name": "alice",
    "created_at": 1710000000,
    "updated_at": 1712000000,
    "person_ids": [
      80011,
      80012
    ],
    "ref_id": ""
  }
}

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

​
Usage

  • At least one of team_id, team_name, or ref_id must be provided.

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 identifying a team by one of ID, name, or external ref.

​
team_id
integer<uint64>

Team ID.

​
team_name
string

Team name.

​
ref_id
string

External reference 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

A team and its membership.