@magecomp Thank you for taking the time to reply - I truly appreciate it very much.
You are correct that using “customer_id”: CUSTOMER_ID_REDACTED does not throw a deprecated warning header. However, it also does not set the customer. My best guess is that the REST API engine just ignores a property it doesn’t understand.
In further testing, I have realized that if you set line_item array’s objects properties other than variant_id and price, it seems to also throw the deprecated warning header. This is true even when setting the quantity property (although it should be noted that it will properly set the quantity, just like using the “customer”:{“id”:CUSTOMER_ID_REDACTED} will correctly set the customer):
{
“line_items”:[
{
“variant_id”:VARIANT_ID_REDACTED,
“price”:25,
“quantity”:1
}
]
}
I have not gone exhaustively through all of the potential order object’s properties, but I have tested various line_item properties (e.g., “fulfillment_status”: “fulfilled”) and all of them I tried outside of variant_id and price cause the deprecated header to be thrown. I even tried it with just the line_item variant_id and quantity like in your example and it threw the deprecated warning header.
Needless to say, getting a deprecated warning when doing simple tasks like creating an order that sets a customer and sets a line item’s quantity to any specific number can’t be correct (and it is in contradiction to the API’s documentation).