This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
In the APIv2 documentation I read:
POST /store/orders/test
POST /store/orders
{
"order": {
"orderNumber": "T1000",
[...]
}
}
and
GET /store/orders/{orderNumber}
{
"order": {
"orderNumber": "T1000",
[...]
}
}
This sounds reasonable (same, clean scheme for the same content). To my surprise I seem to get something different, i.e.POST /store/orders/test
{
"orderInfo": {
"orderNumber": "T1000",
[...]
}
}
andGET /store/orders/{orderNumber}
{
"orderNumber": "T1000",
[...]
}
The variant in the documentation is much cleaner (especially for the status query) and does not require different behaviour depending on the type of call. However I don't expect you changing the API at this point of time. So it might be best to reflect the status quo in the documentation.
One more thing: the order status is described as:
Supplier status of order. Possible values are Processing, Acceptance Required, Created, Submitted, Cancelled, In-Work, Completed.
However, I get back "Complete
" (without the trailing "d"). Again, the documentation should be adjusted.
Hi Stefan,
Thanks for the heads up on the order API documentation discrepancies on https://api-portal.ti.com/store-order-api - they have been corrected.
Best regards,
Paul
**Attention** This is a public forum