I am currently doing some research, and for context I have an API, and I want my API to connect to other Public APIs.
Now, these Public APIs has the ability to connect to Magento. My question is that, Can I use Magento as some sort of a middle man between my API and the Public APIs I want to connect to?
Like if I made a request from my API to Public API 1, can Magento deliver that request to Public API 1? And get the response from Public API 1 to my API?
Any insights is greatly appreciated.
Absolutely you can. I have written extensions that integrated several APIs. For example, processing orders. Check order for validity, hit the vendor api to check stock, hit my own api to check oversize rules or noship rules etc. Then send into a warehouse API to move the order through a status chain. Totally do-able from at least magento 1.6 through 2+ community and enterprise. You can also do it external to magento and hit the magento api depending on your scenario.
Related
There is an API listed in Google APIs (oAuth2) that can be enabled with the service name invoice.googleapis.com. As per the description, it supposedly allows you to fetch Billing invoices for products like Google Adwords, Enterprise etc.
However, there does not seem to be any documentation available online. The PHP client (the one I'm using) also doesn't have an implementation for this.
Does anyone have any more information about this? Is this still in development?
I am new to Amazon marketplace web service (MWS). I have read documentation of web service but I am unable to understand which api suit for update quantity and price of single or multiple product at one time.
Here is link that I am reading so far and don't know where to start.(http://docs.developer.amazonservices.com/en_US/feeds/Feeds_SubmitFeed.html)
Can you guys suggest me where to start?
Check out the feed types. You're going to want to submit a pricing or inventory feed to update your inventory. Once you have a feed created, you submit that using the SubmitFeed operation.
For an overview on how feeds works, check out this What you should know about the Amazon MWS Feeds API section.
Specifically for ASP.NET, there is an SDK built that will help you greatly. If you want to know how to implement that as a web api, that's another topic, but you can wrap code from the SDK inside a web api endpoint. But start with understanding MWS.
What is different between magento extension and rest api?
What is the use of mageto extension and api file?
I am beginner in magento.Anyone plese help me.
Magento Rest API is magento feature to provide us facility to get and set data in magento from third party applications using Rest API. In Magento Rest API there are many functions to get Products data, Customers Data, Orders Data etc. You can check documentation using the below link:
http://devdocs.magento.com/guides/m1x/api/rest/introduction.html
Magento extensions are third party modules that we install to enhance magento by default functionality like ajax add to cart OR add new feature in magento like reward point etc.
I need to download all existing payment information from a paypal account to do some analysis on it, so I set up paypal's ruby rest sdk, which involved creating a new application with its own API keys and whatnot. I can make a successful request with the following:
payment_history = Payment.all( :count => 10 )
However,
payment_history.payments
Is empty.
I'm not sure if this application can only access payments created with it? Can I not get pre-existing payments with the rest api? I would prefer to use ruby, if that's possible, as I would like to keep this all within the simple script I have to analyze similar stripe payments.
Some guidance would be extremely appreciated, as paypal's labrinth of documentation and overlapping APIs have me pretty confused.
You will be able to query only those payments that are made or created with Rest API not the Classic APIs. You can use the Classic Ruby SDKs for the appropriate product to get the Transaction details of the classic APIs
I am developing an API for a social network website. This API will basically get all the requests from the users (get friend list, post a status update etc) and reply back if necessary.
We will implement OAuth 2.0 protocol for authentication. Consumer (our php project) has API id and secret.
Basic scenario:
Client wants to log in
API Consumer (php web project) takes this request, directs user to API
User send his/her user credentials to the api, gets the token.
User comes back to our website, pass token to the consumer.
Consumer goes to the api server, gets the access token.
Now consumer (php project) has access to user's private information.
Since this is a social network website, we want app developers to be able to use our API in the future.
I am not experienced in API-design. Does that flow make sense? I guess the simplest authentication would be accessing user information through php project. But we don't want to access database in php code. We will use ajax in client side and send a request to the API. And I believe there should be a better solution, what would you suggest?
Sure, API design is basically point where you need to choose technology.
Either it can be PHP or .net or Java.
I would prefer either PHP or .Net as we get lot of flexibility in it.
API will return XML or Json depending upon the request.
There are lot of CMS in php which can be helped.
.net we have Service Stack to help you.
API's had to be fully independent from other world as well as within API method as well.
If you are able to achieve this, then you will surely create a good architecture.