Does ProgrammableWeb itself have a web-service API? - web-services

I was wondering if anyone knows if ProgrammableWeb has a service-API, (such as REST), in order to query the repository for information about other services/apps that are published to the website?
Or perhaps even a 3rd-party one, that I so far haven’t been able to find?
If it doesn’t, does anyone know of other services/apps repositories that have APIs where information on the stored services can be retrieved? Such as the ratings by users, tags, etc.

Yes.
http://api.programmableweb.com/

Related

Amazon MWS API - Searching Products

I've recently been trying to gather a small database of books that I have ISBNs for. My options are limited because I need, among other things, a description, which isn't common in services like this. From what I've gathered, one of the best ways to do this is using Amazon's API.
I've been here where people recommended using Amazon's API, and both there and here they mentioned that the old way used in those answers is now deprecated. Unfortunately, Amazon's own documentation for this thing is horrifically terrible, and I can't seem to find any resources to use it.
Does anyone have tips on what to do, or good places to learn how to do this with Amazon? If there are better alternatives, I'm also glad to take those.
I would go about this in two steps:
use Amazon's API to request the store URL of the book in question
details on the API request from the docs.
Amazon's API won't respond with the description you need, but it will respond with the URL of the page which contains that description. All you'll need to do is crawl that page, perhaps with something like npm crawler.
You'll find the description after the <div id="bookDescription_feature_div" class="feature" data-feature-name="bookDescription"> div of the crawled page.

How can I discover existing web services?

I'm sure I sound like a total noob with this question, and I've looked at a couple posts that are basically asking the same question in the title, but the body didn't give anything helpful to my skill or knowledge level.
In this post the OP mentioned that they did some "digging and drilling" to find out that there was a web service in REST format. In another post I found that the OP was using "web console" to look at the activity of a website they were visiting.
I would really like to have more knowledge and methods for finding web services that I can reference and use is some of my new or updated applications, whether RESTful or not. In summary, how do I "dig and drill" to find that a site has a web service I can use programmatically?
The only sensible way to find web services that you can use is to ask.
If the service is intended for your use, then you will be told that.
If the service is not intended for your use, then you will be told that.
If you use a service that is not intended for your use, then that will generally be a bad thing.

Is it viable to set up a store only using magento API?

I am trying to set up a web store using magento on a SOA Architecture. So I intend to use all of the functionalities through the API connecting it with mule ESB.
However on my research I have read that the magento API is Silly Slow. And now I am wondering if it actually can handle the requests of an entire website.
Has anybody done something like this before? Can it actually work? If not, is there a workaround?
Regards
Leo
No, it is not viable to setup a store using only Magento's SOAP and RPC APIs. THat is not the intention of these APIs.
There are examples where people have done what you are looking for such as http://www.yireo.com/software/magebridge
They claim to be 40% faster than native Magento.
I've tried the tool, and it is quite functional.

Web Service Responses of Magento API

Can some people offer some light on the following questions? I believe that the following questions are very much debatable, but I just want to know the mere facts which will enlighten me & of course many others viewing this general question post.
Why does Magento API produces Web Service Responses in XML format & not in JSON format? There should be some advantages in producing the responses in XML format. I want to know those advantages mainly.
In Magento terminology, there are two API versions mentioned - "Normal API" (api/soap) & "API v2 (api/v2_soap)". What's the difference (mainly the advantages) between these two versions, & where does WSDL fit in?
If I'm to create a new Web Service, should I be targeting SOAP v1 format, or the SOAP v2 format, or both of these formats?
Can the Web Service create a general definition of WSDL, based on my requirements, in Magento? What I want is that I want to know whether the "wsdl.xml" file (residing in the "etc" folder of the Magento module) for any particular Magento API module can be generated dynamically? If I provide my required API method name, along with all the property names, types, and also the Response data types, then will I get the "wsdl.xml file dynamically generated with all the Complex Types & Methods & Messages properly mentioned?"
If possible, please provide some good links, from where this spider-webs of Magento Web Services can be thoroughly cleared.
Also, please consider my expertise in this field of Web Service as a novice one, so that based on any valuable input, I can re-frame the question.
Help appreciated & thanks a lot to everybody.
My Main point of asking this question is that I want to make new custom APIs which can be used by any systems, whether it be ERP / CRM / SAP / Cloud / anything in general.
P.S.
I tried posting this question in the Programmers Stack Exchange area, but due to the lack of available required tags (like magento, wsdl & soap), I had to post it here. If possible & required, please transfer this question to proper stack exchange area.
API is not for ajax(frontend), but to integrate Magento (frontend shop) with different ERP, CRM, SAP (backend tools) systems - to import data and get reports. That's why it's using XML.
This is not magento's terminology. This is done mainly for legacy support. So you have to use lates one - v2.
What means general definition of WSDL? WSDL describes published functionality - available calls/resources. If you don't need it you need to overwrite configuration files to not publish everything but only necessary ones or do this form admin area.
Could you tell more clear and more technically what do you need to do with API?
The API works great for normal PHP programming where you want to get something out of Magento. 'Normal' API works fine with PHP, furthermore, the resultant XML is very easy to work with in comparison to the XML that gets churned out by other APIs.
Some people have said that the Magento API is slow, which it is. However, if you move the same code into a Magento program then it still takes forever, the API code isn't much of a burden.

Who is supporting SOAP API

I thought to practice SOAP API. I know it is a time for REST but I thought to give a try to SOAP. I somehow got Flickr.com API supporting SOAP but it has very difficult documentation. No, working examples are available.
Q1. So, do anyone know where I can learn SOAP. Do anyone has SOAP working example for Flickr API
Q2. Any service other than Flickr providing SOAP interface. I saw Google search api has closed new request for SOAP.
regards
SOAP has been largely superseded by REST on the public Internet - as you have noted in your question and has been alluded to in comments.
There are still large users in the Intranet context, companies with an installed base of SOAP, Service Bus, and other concepts that you may well come across if you end up working at one of them. (There are still CORBA users out there also!) When you control both ends of the application, you may have less reason to be flexible using REST.
So if you are looking for useful public implementations you are mostly out of luck.
That said: do create your own services and try them out on your own. Define a service and implement it. Create a client in a different language. Create another client in a third language.
If you are looking for an educational experience, this will lead you down some of the same paths that has lead to REST use in wide-scale disparate systems (and may also shed light on why the public/private has split the way it has)
Good Luck