No, because the request doesn’t return a request ID. This is what it returns:
Exception in Task: Unhandled errors
{"message": "Unexpected error. Please contact a system administrator."}Error getting HTTP response: The remote server returned an error: (400) Bad Request.
This is the request I sent. It’s exactly like above (with the “=” added back into the warehouse ID), except that I removed the newline characters since they seem to confuse the API.
mutation {warehouse_product_update(data: {sku: "70827402-FEL-10689-MS98011T" on_hand: 5 inventory_bin: "Test Bin" warehouse_id: "V2FyZWhvdXNlOjczOTE="}) { request_id complexity }}
This is the query that I have working for the warehouse ID:
{"query":
"query {
account {
complexity
request_id
data {
id
legacy_id
email
username
status
is_3pl
warehouses {
id
legacy_id
identifier
}
}
}
}"
}
I find it strange that the API needs to be told twice what I’m sending it (i.e. a query) before it understands, but for some reason that’s what’s required, so I’m not complaining. I tried that same method with this mutation, thinking maybe it’d work, but still no luck. I tried both of these:
{"query": "mutation {warehouse_product_update(data: {sku: "70827402-FEL-10689-MS98011T" on_hand: 5 inventory_bin: "Test Bin" warehouse_id: "V2FyZWhvdXNlOjczOTE="}) { request_id complexity }}"}
{"mutation": "mutation {warehouse_product_update(data: {sku: "70827402-FEL-10689-MS98011T" on_hand: 5 inventory_bin: "Test Bin" warehouse_id: "V2FyZWhvdXNlOjczOTE="}) { request_id complexity }}"}