You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through my own testing, I learned that the /shipments endpoint incorrectly states that "tracking_number" is required. This had me concerned at first as we ship packages without tracking. After testing, I was able to successfully POST to the endpoint without a tracking number when using USPS as the carrier.
If the tracking number field is conditionally required, it would be quite helpful if additional documentation could be added.
Additionally, the docs state that a successful POST returns code 200, but it actually returns code 201.
The text was updated successfully, but these errors were encountered:
justinmcdaniel
changed the title
/shipments endpoint has some incorrect information
/shipments endpoint documentation has some incorrect information
Apr 18, 2023
Thanks for passing this feedback over. I've sent the information over to our product team so that they can review it and make the necessary updates to our documentation. We appreciate you bringing this to our attention.
Through my own testing, I learned that the /shipments endpoint incorrectly states that "tracking_number" is required. This had me concerned at first as we ship packages without tracking. After testing, I was able to successfully POST to the endpoint without a tracking number when using USPS as the carrier.
If the tracking number field is conditionally required, it would be quite helpful if additional documentation could be added.
Additionally, the docs state that a successful POST returns code 200, but it actually returns code 201.
The text was updated successfully, but these errors were encountered: