Skip to main content
Bulk endpoints reduce request count and make large sync jobs easier to manage.
Bulk responses preserve input order, including duplicate input values. Missing records return per-item errors instead of failing the full request.

Endpoints and limits

All bulk endpoints accept:
string
Required for guild-scoped keys. Optional for global keys.
boolean
Defaults to false. Adds resolved profile data when allowed by the endpoint and plan.

Discord bulk

cURL
string[]
required
Discord user IDs to resolve. Maximum 50.

Roblox bulk

cURL
string[]
required
Roblox user IDs to resolve. Maximum 50.

Alt bulk

cURL
string[]
required
Roblox user IDs to use as alt-detection seeds. Maximum 10.
Alt bulk is Premium-only for normal API keys and has a smaller limit because each lookup performs heavier detection work.

Response shape

200 OK

Result fields

object[]
required
Ordered result list matching the input order.
object
required
Original input value for this item.
boolean
required
true when Dock found a valid result for this item.
object | null
required
Per-item lookup data when found is true.
object | null
required
Per-item error when found is false.
number
required
Number of results with data.
number
required
Number of results with LINK_NOT_FOUND.
number
required
Number of results that failed for reasons other than not found.

Best practices

  • Use bulk endpoints for sync jobs, dashboard hydration, and moderation queues.
  • Keep resolved=false unless the UI needs expanded profiles.
  • Retry only the items that failed for retryable reasons.
  • Respect Retry-After if the top-level response is 429.