findById

Retrieves detailed information about a specific user’s multi-account associations. This endpoint returns the account IDs that have been linked to a particular user, helping you investigate individual cases of multi-account usage.

Endpoint

GET {base_url}/api/v1/{account_id}/projects/{project_id}/multiaccounts/{id}

Authentication

Requires API key authentication:

Authorization: Bearer {api_key}

Path Parameters

Response Structure

The response returns an array of account identifiers associated with the specified user:

["string", "string", "string"]

Each string in the array represents a unique account ID that has been linked to the same user.

Example Response

["1", "5", "10"]

This response indicates that accounts with IDs “1”, “5”, and “10” are all associated with the same user.

Example Response (Detailed)

[
  "acc_abc123",
  "acc_def456", 
  "acc_ghi789"
]

This indicates three separate accounts have been detected as belonging to the same user.

Use Cases

• Fraud Investigation: Deep-dive into specific users suspected of multi-account fraud
• Account Linking: Understand which accounts are operated by the same individual
• Ban Enforcement: Identify all accounts that should be banned when one account violates policies
• Customer Support: Investigate user reports of account issues or false positives
• Forensic Analysis: Trace account relationships during security investigations
• Abuse Pattern Analysis: Study how specific users create and use multiple accounts

Interpreting Results

• Empty array []: No multi-account associations found for this user ID
• Single item ["1"]: Only one account detected (no multi-account behavior)
• Multiple items ["1", "5", "10"]: Multiple accounts detected from the same user

The number of accounts in the response indicates the severity of multi-account usage:

• 2-3 accounts: May be legitimate (e.g., test accounts, family members)
• 4-10 accounts: Likely policy violation or moderate abuse
• 10+ accounts: Strong indicator of fraud or systematic abuse

Important Notes

• The id parameter should be a user identifier from your system that was passed to BotBye
• Account IDs in the response correspond to identifiers from your application
• This endpoint is useful for investigating specific users flagged by the “Find by Project” endpoint
• Consider the context when evaluating multi-account associations (shared devices, legitimate use cases)
• Use this data in combination with your own signals for accurate fraud detection
• Implement appropriate privacy controls when storing or displaying multi-account association data

Error Responses

• 404 Not Found: The specified user ID has no multi-account data or doesn’t exist
• 403 Forbidden: Invalid API key or insufficient permissions
• 400 Bad Request: Invalid account_id, project_id, or id format

Accepted permissions Project → Multi Account → Multi account

Token scope Multi Account View