Skip to main content
POST
/
team
/
infos
Batch get teams
curl --request POST \
  --url 'https://api.flashcat.cloud/team/infos?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "team_ids": [
    1001,
    1002
  ]
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "items": [
      {
        "team_id": 1001,
        "team_name": "Backend SRE",
        "person_ids": [
          80011,
          80012
        ]
      },
      {
        "team_id": 1002,
        "team_name": "Frontend",
        "person_ids": [
          80013
        ]
      }
    ]
  }
}

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

  • Up to 100 team IDs per request.

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 for batch team lookup by IDs.

​
team_ids
integer<uint64>[]
required

List of team IDs to look up. Max 100.

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

Batch team info result.