We wanted to create a Spree app where the entire front-end is a single-page app.
What is the recommended approach for this?
As part of the same, we were exploring the Spree API endpoints required to be used from the front-end.
Are there any references or guides we can follow, particularly on the implementation of the checkout process?
We couldn't find any API documentation on creation of shipping address and billing address during the checkout process.
We tried sending a POST request to the addresses API controller, but there were only the show and update methods there
We tried a PUT request on the orders API controller by passing parameters such as orders['bill_address_attributes']['...'], orders['bill_address']['...'], but we received status 422.
We also tried a POST request at /checkout/update/address, but we got route not found error.
We have not been able to find a method to create shipping and billing addresses in the 'address' phase of the checkout flow.
Are there further references where we can find details on this?
Any pointers to documentation or source code regarding the above would be of great help.
The checkout workflow is a little tricky, but going through each step of the checkout process defined here will work.
But, I'm sure you've looked at that and it isn't so easy to follow, but not to fear, Spree has a walkthrough online that will make it easier to soak up:
https://github.com/radar/spree_api_examples/blob/master/examples/checkout/walkthrough.rb
Related
I need to create a solution for altering the checkout process.
Better said, I need to add some functionality to it with a remote app (I am not sure if this is the right way to do it).
Mainly, what is needed represents a process that calls an external API, using a private API key from a delivery company, that registers a pick-up from the buyers house and sends the product to our headquarters.The process should be started when the user completes the entire checkout system from shopify, after payment.
After that, some AWB should be returned to the users checkout page, or some response regarding the creation of the pick up.
My question is, let's say, using some language like javascript with node and Koa or express, how one can achieve that? I can't find any tutorials or something that would help me do this.
I'm working on a cloud project and I have to use Contrail it provides a RESTful API to use, but it is documentation is too small. I would like to know how to perform rest requests, especially post requests on "project" resource.
Each Contrail config node provides supported API details(searchable) at http://:8082/documentation/index.html
You could also check here which is a bit old but should serve your project API needs.
Your question is old, but as there are no other answers I thought I would contribute one. Were you interested in an answer or just wanted to share the documentation you'd written? I agree with you that Contrail documentation is very scarce, and every attempt to contribute to it should be appreciated. I had to integrate with Contrail API a while ago, and found out that in some cases I had to call OpenStack APIs to get the job done (Contrail is built on top of OpenStack). Project and user management were some of them.
I wrote a documentation about Contrail api, For each resource I mention the allowed methods and which parameters to integrate on the request body and I test it until I get it to work finally I put an example. I haven't finished the documentation, I stopped working on Open Contrail. The documentation is my personal try maybe it would be useful and maybe it contains some mistakes, Thus, I would like to share it. You can find it here.
How to use the 2Checkout payment integration with Odoo. I have gone through their documentation but i have no idea how to develop the module in odoo to integrate 2checkout.Is there any guideline for that. If there is any examples that would be helpful to me.
There is not a guideline for creating custom payment processors, however you can take ones that already exist and replace the processors logic with logic for 2Checkout.
The easiest one is the Ogone module: https://github.com/odoo/odoo/tree/8.0/addons/payment_ogone
In fact, you'll find the Odoo developers doing the same thing. I occasionally saw an Ogone reference in other payment modules accidentally left in.
Basic Requirement for any payment gateway:
1) Go through the document, where you can find what data are required to
send in request and what response you will get.
2) Generate the request and send it from your module, you will get
response.
3) Now, as in odoo every response from the payment gateway is sent to the
web so to handle you need to design some web template.
4) And in the web controller you can do all the process that you need to do for the order or invoice.
You can do this with the default payment gateway like paypal or Bukaroo available in Odoo.
Hope it will help you.
We have a custom integration that uses Shopify API. Changes to the schema breaks the integration. Today we have found The field Source has been removed and 3 fields have been added in its place: source_identifier , source_name and source_url. (orders api)
Is there a way to get information on coming changes, so we can be pro-active, rather than waiting for our integration to break in production and look for the changes while our fulfillment service waits?
Better late than never ;) I suggest you checkout the API Accouncements topic in the Shopify forum, as that is where all important API changes are posted:
https://ecommerce.shopify.com/c/api-announcements
Note: You can subscribe to the topic, so whenever something new is posted you'll automatically get an email notification.
Will there be an "activity" endpoint for us 3rd Party developers to use so we may build apps that have the same information as the "official" apps?
Even piecing together data from other endpoints we cannot build such a feature since there's no way for us to get checkin history for users other than "self". We can only get other users last checkin.
Thought I'd read some time ago that the website and official apps were just going to use the api so there must be some hidden/not public endpoints.
Just curious.
The official app does use the same endpoints exposed through the API, but the public API is only a subset of what the official app uses :) (e.g., we don't allow account creation)
Having said that, there's currently no "activity" endpoint we expose, nor will we likely expose one in the future. Sorry bout that!