Get bulk update job details
GET
/v1/users/bulk-update/{id}/details
What this endpoint does
200 with zero counts, not 404. Use status as the gate before treating details as processed output.INFO
_id → poll status until Completed → GET /v1/users/bulk-update/{id}/details.Quick start
<jobId> with a 24-character job ObjectId.Authentication and permission
Authorization: Bearer <COMMUNITY_API_KEY>. Required permission: getBulkUpdate. Keep the key server-side.Complete examples
message is Bulk update details fetched successfully. Envelope { status: "success", message, data: { successUsers, failedUsers, pagination, data } }.status, email, and the columns that job wrote.successUsers: 0, failedUsers: 0, empty pagination. That is not the same contract as status (500 Bulk update not found).Bulk update ID is required and must be a valid ObjectId.Success and readback
200. Use status=Completed on the sibling status route before treating data[] as processed output.CHECK
500 Bulk update not found means the id did not match. Details 200 with zeros can mean the same missing id, or a job with no processed rows. Confirm _id on the list.Errors and recovery
| Status | When | Recovery |
|---|---|---|
400 invalid ObjectId | Malformed {id} | Send a 24-character hex id from the list. |
401 | Missing or invalid token | Add a valid community key. |
Retry safety
TIP
Gotchas
Completed.status casing can differ from the status endpoint. Compare job _id.Next steps
Request
Path Params
Query Params
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://adss-integration.returning.ai/apis/v1/users/bulk-update//details?page=undefined&limit=undefined'Response Response Example
200 - Example 1
{}Modified at 2026-08-19 13:43:30