Overview
This endpoint is used to change order statuses by performing some of the bulk actions available on the Manage Orders page in Sellercloud.
To consume this endpoint, you must:
- Be authenticated.
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 when updating the order.
Endpoint
An example of such an endpoint for XX server is:
https://xx.api.sellercloud.com/rest/api/Orders/Statuses
For your server endpoint will be:
https://{your_server_id}.sellercloud.com/rest/api/Orders/Statuses
Request
- Method Type: HttpPut
- Authorization: Use Bearer Token + token received from token authentication
- Header info: Content-Type: application/json
- Body data:
| Parameter | Data Type | Description | Required |
| OrderIDs | list/int | List of valid existing Sellercloud Order IDs. | Yes |
| Action | enum | Provide one action from the list below.
The same action will be performed for the whole list of orders provided in the call. |
Yes |
Actions
The list below provides the enumeration values for the currently supported bulk actions:
- Set Channel Notified For Shipping = 0
- Set Channel Not Notified For Shipping = 1
- Set Invoice Sent To Channel = 2
- Set Invoice Not Sent To Channel = 3
- Set Shipping Requires Third Party = 4
- Set Shipping Does Not Require Third Party = 5
Request Format
{
"OrderIDs": [
0
],
"Action": 0
}
Response
- If the user is authenticated and the request is successful, then the response will be Status Code 200 => OK. If you selected actions 4 or 5, you will also receive a Queued Job ID in the response. For all other actions, this field will be “null”.
- If the user is not authenticated, then the response will be Status Code 401 => Not Valid Token
- In case of an error, the response will be Status Code 500 => Internal Server Error
- In case of an incorrect request, the response will be with status code 400 Bad Request