Skip to main content
POST
Batch get persons

Restrictions

Usage

  • Including the account ID returns the account owner, with as account. Other IDs are looked up among the account’s members, including removed ones (status deleted), so IDs saved in older records still resolve.
  • Duplicate IDs are deduplicated; IDs that match neither are omitted.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Get person info by IDs request

person_ids
integer<uint64>[]
required

Person IDs to look up — these are member IDs (get them from POST /member/list). Passing the account ID returns the account principal; unknown IDs are ignored

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

Person info by IDs response