i want to know is there any tool/product/library to call rest api and process its output, add some conditional logic to further call another rest api call. Something similar to yahoo pipes.
The tool should have a UI to configure all these instead of writing a program.
I think you are looking for Postman.
Link: https://www.getpostman.com/
Related
When I hear API, I think the only way to use an API is to write a program to call the functions provided by the API.
Is writing a program the only way of using a RESTful API?
It seems that we can use curl to use RESTful API in https://developer.github.com/v3/guides/getting-started/. So how is that possible without writing a program to call the functions provided by a RESTful API?
Thanks.
There's no reason you can't invoke a RESTful API via a utility such as curl.
However, it only works for the simplest of use cases.
Most use cases have several steps that simply work better through automation. From creating or interpreting the payloads that are sent/received from the API calls, to orchestrating several calls in a larger transaction.
Also, consider, if you put your curl command in to a script file, then, well, that's "programming".
I'm looking to make a soap call in order to setup information for a series of tests.
In order to do this, I want to call an established soap request. I'm using gatling for the tests, so I'd like to do the data setup with scala/gatling as well. Is this something that can be easily done, and can one of you FINE PEOPLE show me an example of how?
I need to be able to send REST calls and save the returning payload to variables within the cookbook (using chef solo).
Calls are made in HTTPS
Need to be able to get returning cookie header in order to login to API
Is there such a community LWRP available? I am not aware of any built-in functionality within chef to allow this. (from what I've read http_request provider in chef does not answer the above criteria)
Resources (and thus LWRPs) don't really have output values. What you want is to just use the Chef::HTTP class:
val = Chef::HTTP.new('https://cmdb/').get('/')
I am currently in the throes of writing a plugin for Bugzilla, and so all of the code needs to be written in Perl. I have everything working quite nicely, however there are a few places where I know I need to do multiple requests to the same REST server, and, given that it might be distant network wise, I would like to be able to send several requests, and then wait for them all to come back, rather than do the Stop-And-Wait Send/Wait/Send/Wait.
Using REST::Client allows for very easy access to REST client functionality, which is what I am currently using. The top Google result for perl sync rest is HTTP::Async, but this page doesn't address REST directly, and it is not clear to be how to easily use HTTP::Request to easily process them.
What is the best way to do this?
Mojo::UserAgent is a very nice web agent that does async well.
I want to ask some questions about the REST call. I am the green for the REST call and I would like to like what is REST call and how to use the URL to send a REST call to the server. Can anyone give me some basic tutorial or link for my to reference?
Besides, if I want to send a REST call to the server, what should I do? Do I need to set something in the URL? or set something in the server? Thank you.
REST is just a software architecture style for exposing resources.
Use HTTP methods explicitly.
Be stateless.
Expose directory structure-like URIs.
Transfer XML, JavaScript Object Notation (JSON), or both.
A typical REST call to return information about customer 34456 could look like:
http://example.com/customer/34456
Have a look at the IBM tutorial for REST web services
REST is somewhat of a revival of old-school HTTP, where the actual HTTP verbs (commands) have semantic meaning. Til recently, apps that wanted to update stuff on the server would supply a form containing an 'action' variable and a bunch of data. The HTTP command would almost always be GET or POST, and would be almost irrelevant. (Though there's almost always been a proscription against using GET for operations that have side effects, in reality a lot of apps don't care about the command used.)
With REST, you might instead PUT /profiles/cHao and send an XML or JSON representation of the profile info. (Or rather, I would -- you would have to update your own profile. :) That'd involve logging in, usually through HTTP's built-in authentication mechanisms.) In the latter case, what you want to do is specified by the URL, and the request body is just the guts of the resource involved.
http://en.wikipedia.org/wiki/Representational_State_Transfer has some details.