Get All Purchase Orders
In order to retrieve metadata for existing purchase orders, you must:
- Be authenticated user
Information on how you can authenticate: Authentication
As soon as you do authentication and receive a valid token, it needs to be passed on the call for getting purchase orders.
You can do additional filtering and pagination on the purchase orders.
Example for such endpoint for TT server: https://tt.api.sellercloud.com/rest/api/purchaseorders?pageNumber=1&pageSize=1
Information about expected request parameters and their type can be found on swagger UI https://tt/api.sellercloud.com/rest/swagger.
- Method Type: HttpGet
- Authorization: Use Bearer Token + token received from token authentication
- Header info: Content-Type: application/json
Number of page
Number of purchase orders per page
List of IDs of purchase orders
List of IDs of companies
Saved,Ordered,Received, Pending,Cancelled, Competed.
None, PartiallyReceived, FullyReceived
Minimum creation date
Maximum creation date
NoPayment, Authorized, Charged, Uncleared, PartiallyRefund, eBayPaid, PaymentError
Important: That filter should only be utilized if client setting "Enable vendor invoices workflow" is disabled.
Is Inventory Count Enabled
0: No, 1: Yes
Is Vendor Invoiced . This filter should only be utilized if client setting "Enable vendor invoices workflow" is enabled.
Is Approved, 0: No, 1: Yes
A search term for performing a global search. No
- If user is authenticated and provides a valid token, then response will be Status Code 200 => OK and purchase order metadata in JSON format
- If user is not authenticated, then response will be Status Code 401 => Not Valid Token
- On server response => Status Code 500 => Internal Server Error