API for Cart

Core doesn't support uuid mapping in API calls. JSON API module provided this.

fwiw, I think this proposals misunderstands the REST verbs a little bit. Consider the following basic guidelines:

• GET should return a collection or an item resource; so a GET on /node should return a collection (or list) of nodes, while a GET on /node/1 should return a single node.
• POST to a collection resource should create a new item in that resource.
• DELETE to a collection or an item resource should delete the resource.
• PATCH should perform a partial update on a resource (and I prefer JSON Patch for the media type on these requests, but I'm willing to go along with core ; ).

For a cart resource, this means a GET to /carts should return all carts the API consumer has access to and /carts/## should return a single cart assuming the consumer has access to it. A POST to /carts should create a new cart order for the API consumer (and I'm fine with having a shortcut like that versus requiring the consumer to know how to create a cart solely through /orders), but to /carts/## would be nonsensical. The best shorthand you could achieve would be a collection resource whose URI includes the cart ID, like /carts/##/order-items. However, in that case, I tend to think we should really just be submitting a POST to the /order-items resource, and the body should include the ID of the cart order this sucker is goin' on.

I documented a lot of this in the Commerce Services project for Commerce 1.x. That project page includes a link to the indispensable e-book on API design from Apigee with the best practices that guides the above. I also posted a complete API user guide to https://www.drupal.org/node/2043077#comment-10105608, which defines how our resources worked and what they are. I'd expect us to do something equivalent inside Commerce 2.x, though we may need to modify it to conform with the Drupal community's idiosyncrasies here and there. Would need to discuss the differences on a case-by-case basis I'd imagine.

No patch.

Is anyone working on this?

I'm looking into building a headless Drupal Commerce installation which would be shared between multiple D8 sites.

So, what is the plan to do this job? commerce_services module seems deprecated, last update is 2014, and there is no any plan of Commerce 2.x

is there any guideline for developing of ios/android applications in Commerce 2.x

i found the things may help:

• drupal core module REST, bring CURD operation for all entity, and let us defind REST resource by using Plugin System.
• drupal core module User, provides some endpoits for login/logout/reset-password/register users in cookies auth
• the jDrupal contrib module for js lib to use above APIs.
• ths Services contrib module provides tools for building None-RESTful APIs

no more ways to do.

good, need help? I'm in

I want help too. @jgrunert, how can we help you?

Assigning to myself. I had a good discussion at Florida DrupalCamp about ways forward. I've written a draft proposal that I'm having reviewed before posting here.

Ping me about this. We can put some time into it too.

I am making production project that need this features right now.
I am planing to complete this features in a week.

@mglaman where can see your draft proposal ? can't you share it to me right now ?

@"164713332@qq.com" and others
https://github.com/mglaman/commerce_cart_api

Changing the status, since we now have a functional Cart API that needs to be either merged into Commerce or made into a contrib project.
We're currently discussing the implementation with the JSON API team, to see whether cooperation is possible on that side.

Please note: if you choose to use that repository, add the following to your composer.json

        "commerce_cart_api": {
            "type": "vcs",
            "url": "https://github.com/mglaman/commerce_cart_api.git"
        },

Be aware it is experimental and will change without notice. Some were bitten by a refactor in a rest.module plugin change (see https://github.com/mglaman/commerce_cart_api/commit/620679f73c085253107d...)

Especially since a goal is to solidify this at DrupalCon.

Sorry for any "silence" on this. Just have not wanted to say "check this out!" then cause breaking changes.

thank you so much.

https://github.com/mglaman/commerce_cart_api/pull/10

@mglaman
I found some mistake of the code, I had fixed it, please check my PR.
Im sorry that I forgot to create an new branch.

It lives: https://www.drupal.org/project/commerce_cart_api

https://commerceguys.com/blog/introducing-cart-api-drupal-commerce