Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WEBAPI: Missing shipping method detail in salesOrderRepositoryV1 GET response #3375

Closed
karanbhomiagit opened this issue Feb 11, 2016 · 3 comments
Closed

WEBAPI: Missing shipping method detail in salesOrderRepositoryV1 GET response #3375

karanbhomiagit opened this issue Feb 11, 2016 · 3 comments
Assignees
@NadiyaS

Comments

@karanbhomiagit
Copy link

When I am making a GET call to the salesOrderRepositoryV1 REST API, the response json does not have "shipping_method" field in it.

API :
GET /V1/orders/{id}
GET /V1/orders
@pboisvert
Copy link

@mbrinton01 do we have this captured in the backlog?

@mbrinton01
Copy link

@karanbhomiagit we have a shipping method in that API under:

"shippingAssignments": [
      {
        "shipping": {
          ...
          "method": "string"

Does this work for you?

@NadiyaS
Copy link
Contributor

NadiyaS commented Jun 21, 2016

this issue is a duplicate of #2628 and had been fixed already.
Shipping data is transmitted to extension attributes.

@NadiyaS NadiyaS closed this as completed Jun 21, 2016
magento-team pushed a commit that referenced this issue Nov 28, 2018
@dvoskoboinikov
Merge pull request #3375 from magento-qwerty/2.2.7-bugfixes-251018
bdff263 
Fixed issues:
- MAGETWO-92172: [Backport for 2.2.x] Redundant File Names for Quote Attachments
- MAGETWO-92725: Incorrect group actions behavior
- MAGETWO-92181: Fixed incorrect behavior of attribute sets
- MAGETWO-92184: JS Templates Limitations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NadiyaS NadiyaS

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pboisvert @MomotenkoNatalia @mbrinton01 @NadiyaS @karanbhomiagit