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
While working on our Ruby client, I encountered several issues in the spec:
Duplicate Operations
linkCarrierAccount appears twice with different HTTP verbs (PUT and POST). Should PUT be removed?
Inconsistent HTTP Verb Usage
Several “get” operations use PUT instead of GET, e.g.:
getCarrierAccounts -> PUT /shipping/v2/carrierAccounts
getCollectionFormHistory -> PUT /shipping/v2/collectionForms/history
getUnmanifestedShipments -> PUT /shipping/v2/unmanifestedShipments
Poor descriptions
Some descriptions are unclear, e.g.:
getCarrierAccounts -> "This API will return Get all carrier accounts for a merchant."
We worked around the duplicate method in our code generator but left other inconsistencies as is. Fixing these in the spec would improve usability for all.
The text was updated successfully, but these errors were encountered:
Hi @hakanensari,
thanks for reaching out!
I'll forward your feedback to the respective team. Thanks for letting us know!
Best,
Marc
Selling Partner Developer Services
While working on our Ruby client, I encountered several issues in the spec:
Duplicate Operations
linkCarrierAccount
appears twice with different HTTP verbs (PUT and POST). Should PUT be removed?Inconsistent HTTP Verb Usage
Several “get” operations use PUT instead of GET, e.g.:
Poor descriptions
Some descriptions are unclear, e.g.:
We worked around the duplicate method in our code generator but left other inconsistencies as is. Fixing these in the spec would improve usability for all.
The text was updated successfully, but these errors were encountered: