Better management of multiple APIs and endpoints

[GoogleCodeExporter]

First off, I love this app. It's my favorite and I've donated to prove it. But 
I do have a wish. ;)

Like many (hopefully most?) web service devs, my apps are iteratively deployed 
to separate environments in their lifecycle - dev, ci, staging, production - 
the usual. Obviously, the API is substantially the same across those 
environments. The saved requests list, which is currently flat, is not 
conducive to organizing multiple endpoints like that. What I have to do is keep 
all my requests saved for one particular environment (dev), and when I need to 
hit one of the others, I select it, then go copy the alternate endpoint URL 
from somewhere, carefully select the schema://host part of the URL and paste 
over it. I may have to do this dozens of times in a session.

What I'd really like to see is something like this: the ability to add/remove 
named APIs or projects, with the ability to select which one I'm currently 
working with. Within a given API, I'd like to be able to put in multiple 
endpoints specific to that API. Saved requests would be per-API, as well, but 
would only represent the path part of the API that simply gets appended to the 
endpoint when I click "Send Request".

So a usage sequence might be:

1. Click on the API I'm working with.
2. Select the (previously entered) dev endpoint.
3. Repeatedly select and send requests associated with that API to that 
endpoint.
4. Select the (previously entered) staging endpoint.
5. Repeatedly select and send requests associated with that API (same list as 
3) to *that* endpoint without any copying/pasting.
Etc...

Bonus points: the ability to associate a set of headers with an endpoint that 
are always sent in requests to that endpoint (in my case, specifically to avoid 
having to paste in an auth token for each individual request being sent - I'd 
just put the token in the endpoint headers once instead).

If this happens, I'd donate some more and I think I could get a couple of 
buddies to do so, as well. Thanks again for the awesome tool, I'd love you see 
you take it to the "next level". :)

Original issue reported on code.google.com by m...@nerone.org on 16 Apr 2012 at 9:24

[GoogleCodeExporter]

This is really good idea :)
I'll do it. But it takes some time. Probably i'll start at the weekend.

Original comment by jarro...@gmail.com on 17 Apr 2012 at 8:12

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Just wondering if you're still planning to do this.

Original comment by m...@nerone.org on 25 Jul 2012 at 5:13

[GoogleCodeExporter]

Yep! :)
Just check my blog http://restforchrome.blogspot.com
I have rewritten almost whole application. From scratch (see new RestClient 
project in trunk).
Still it takes some time to implement all new functionalities. I think it will 
be made in next two months. Mostly because that I want to use part of Chrome 
API that is available in dev channel only. In this time current dev channel 
should become stable.
Will see. Maybe I finish new version earlier and will update the application 
without this part of API but it depends on my free time. Believe me, I spent 
most of my free time working on this project. 

Original comment by jarro...@gmail.com on 25 Jul 2012 at 5:51

[GoogleCodeExporter]

That's awesome! Your description in the blog illustrates having a query 
argument (the API key) be inserted per-endpoint. Will the same be true of 
headers (several of the services my app accesses use an Auth-Token header)?

Original comment by m...@nerone.org on 25 Jul 2012 at 10:02

[GoogleCodeExporter]

It is fixed in revision 150. It will be available in next update.

Original comment by jarro...@gmail.com on 27 Sep 2012 at 3:50

• Changed state: Fixed