Overview
This endpoint can be used to delete the tracking numbers on a single existing Purchase Order. Note that it will only work if the Client Setting Enable Multiple Tracking Numbers On PO is enabled.
To consume the endpoint, you must:
- Be an authenticated user.
For information on how you can authenticate, see Authentication.
After you authenticate and receive a valid token, you must pass it to service calls.
Endpoint
An example of this endpoint for XX server is:
- https://XX.api.sellercloud.com/rest/api/PurchaseOrders/{id}/TrackingNumber/Multiple
For your server, the endpoint will be:
- https://{your_server_id}.api.sellercloud.com/rest/api/PurchaseOrders/{id}/TrackingNumber/Multiple
Request
- Method Type: HttpDelete
- Authorization: Use Bearer Token + token received from token authentication
- Header info: Content-Type: application/json
Request Body
| Parameter | Parameter Type | Data Type | Description | Required |
| id | path | Integer | ID of the targeted Purchase Order. | yes |
| TrackingNumbersIDs | body | array | List of the IDs of existing tracking numbers to remove from the targeted PO. You can use the Get PO Shipping Information endpoint to retrieve the IDs. | yes |
The request body should be formatted as follows:
{
"TrackingNumbersIDs": [
0
]
}
Response
- If the user is authenticated and the request is successful, the response is Status Code 200 => OK
- If the user is not authenticated, the response is Status Code 401 => Invalid Token
- In case of an error, the response is Status Code 500 => Internal Server Error
- In case of an incorrect request, the response is Status Code 400 => Bad Request