Hey @edstevo - that definitely seems a bit odd for sure. Looking at our docs here: reverseDeliveryCreateWithShipping - GraphQL Admin, it doesn’t seem like the label or tracking inputs are necessarily marked as required fields (just the reverseDeliveryLineItems and the reverseFulfillmentOrderIdreverseFulfillmentOrderId).
Could you share the full mutation call you’re using including the inputs. If you’re able to share the X-Request-ID header from the response headers we send out, that would be helpful too. I can check our logs if you are able to share that request ID and investigate further on our end here.
I can’t replicate this request right now because I’ve had to manually add the relevant details via the Admin dashboard. So I can’t “create” the reverseDelivery again. But the error message is valid. See attached:
It looks like when a reverse delivery is created without either the tracking info or the label info, we’ll return that error. If you include both though, it should work like this:
Could you let me know if the above formatting works for you? I just tested it on my end here and I was able to create a reverse delivery using the mutation in my last example there on my test shop. Hope this helps!
Hi - I haven’t had another return requested yet, so I cannot confirm this has been resolved. I don’t have test credentials to trigger a fake “return” either.
As you can see the payload has both labelnput and the tracking details. My customer needs to download the label as well as have access to the tracking number.
The error says “must receive either return_label_file or tracking_info”.
I’m not sure what happened here, but the mutation wasn’t copied over correctly from the documentation. I copied it over again today and it had more inputs specified and it now works fine.