Overview
This endpoint can be used to add serial numbers for PO.
In order to consume the endpoint, 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 to the call.
Endpoint
An example of such an endpoint for XX server is https://xx.api.sellercloud.com/rest/api/PurchaseOrders/Serials
For your server endpoint will be:
https://{your_server_id}.api.sellercloud.com/rest/api/PurchaseOrders/Serials
Request
Method Type: HttpPost
Authorization: Use Bearer Token + token received from token authentication
Header info: Content-Type: application/json
NOTE: Serial numbers can only be added for products that do not have serial numbers already added. This can be checked by calling rest api service ‘GET /api/PurchaseOrders/Serials’
Request Body
| Parameter | Data Type | Description | Required |
| PoSerialNumbers | List<PoSerialNumber> | List of serial numbers to add | Yes |
| PoSerialNumber.ReceivingID | Integer | ID of the receiving.
Can be obtained from rest api service ‘GET /api/PurchaseOrders/Serials’. |
Yes |
| PoSerialNumber. ProductID | String | Product ID | Yes |
| PoSerialNumber.SerialNumbers | List<ProductSerialNumber> | List of the serial numbers to add for the product in the specified receiving. | Yes |
| ProductSerialNumber.SerialNumber | String | Serial number for the product | Yes |
| ProductSerialNumber .Notes | String | Serial number notes.
Can be omitted if no need to be set. |
No |
Response
- If the user is authenticated and the request is successful, then the response will be Status Code 200 => OK
- 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