you can see this is the Bad URL as API think the Order number is “M-00588371” and after “/” are the actions and that’s why API return with “Order number Not Found” as response of above URL.
screenshot “Order Number with Bad API URL.png” for more details
When I search this Order number on Ordoro’s dashboard it converted the “/” in Order number to “%2F”
screenshot “Order Number and URL.png”
So, I tried the same method but it failed and API returned with “Internal Server Error” Message
Hi,
Can you please send an example of the request and response using CURL or a similar tool? That will help us eliminate the UriBuilder as a potential source of the problem. In the response you should see a header titled X-API-REQUEST-ID which should also include in your reply to help us diagnose any issues on our end.
I tried it with cURL and it seems to be working fine.
as it return with following response
“{“error_message”: “A tracking for shipment ‘M-00588371/002-1’ already exists.”, “param”: null}”
Ah, it appears that order has already been shipped. Once an order has been shipped it cannot be shipped again without first deleting any labels or tracking. Since this order was probably just marked as shipped or had tracking manually applied, you can use the DELETE /order/<order_number>/shipping_info endpoint to unship it.
Unfortunately I cannot help you with your code. You can probably reach out on a C# specific programming forum to see why the request is getting encoded incorrectly.