Overview
In order to get information for the bulk update log regarding a queued job, you can consume the endpoint presented in this article. In order to consume it, you must:
- Be authenticated user
For information on how you can authenticate, see: Authentication
As soon as you do authentication and receive a valid token, it needs to be passed on the call for receiving the bulk update log details.
- Have valid ID of an existing queued job
Endpoint
Example for such endpoint for TT server is:
https://tt.api.sellercloud.com/rest/api/QueuedJobs/BulkUpdateLog/{ID}
For your server endpoint will be:
https://{your_server_id}.api.sellercloud.com/rest/api/QueuedJobs/BulkUpdateLog/{ID}
Request
- Method Type: HttpGet
- Authorization: Use Bearer Token + token received from token authentication
- Header info: Content-Type: application/json
- Parameters: ID of the existing queued job
- Queued job type must be of Product_Bulk_Update
| Parameter | Data Type | Description | Is Required |
| id | integer | ID of existing queued job | Yes |
Response
- If user is authenticated and provides a valid ID of a queued job, then response will be Status Code 200 => OK and bulk update log metadata in JSON format
- If Queued job ID is invalid and job cannot be found => Status Code 404 => Not Found
- If Queued Job Type is different from Product_Bulk_Update => Status Code 400 => Bad Request
- If user is not authenticated, then response will be Status Code 401 => Not Valid Token
- On server response => Status Code 500 => Internal Server Error