johns

Check out jsonapi.org

When your heart betrays your mind.

ngrok is functionally equivalent to our Passageway: runscope.com/docs/passageway. Can never have enough tools out there though. Looks great Alan.

Why reuse the name? That's just confusing (and a bit disrespectful).

Thanks, it's fixed now.

This is one of the reasons we built Runscope (yes, shameless plug). Seems like no amount of documentational diligence will completely prevent wire gremlins. Whether its faulty SDKs, typos, etc. if you can't see what's on the wire and share that with the party on the other end you'll waste hours debugging unfixable problems.

You can delete requests and buckets on demand.

Some of our customers are running it in production apps but for the most part you turn it on to solve a problem then turn it off when you're done. Down the road we'll be making production use more useful with the security concerns you mention at the forefront.

If anyone has any API debugging questions, feel free to let me know.

Different building. Twitter was at 795 Folsom (at 4th) which was also an AT&T building. This building is at 2nd and has very few windows and does not appear to be occupied by any office tenants (I walk by it every day).

Once people stop calling it the wrong thing, the discussion can be about something else.

I also hate this nitpicking, but it's clearly not going away so you're better off not inviting it by using the term incorrectly.

It helps no doubt (though the signed out site is not using it that extensively), but you still have to pay attention to the details. Our designer did an amazing job with it.

It's always bugged me when I went to a blog post for a new company and it was completely detached from the main site. Looks like we maybe went too far the other direction :D

Hmm that's a good idea. Let me work on that.

OK, done: https://www.runscope.com/oauth_tool

I haven't had a chance to get that into the docs and editor yet. Will do soon.

Won't help...for now. We don't have any specific plans around that yet, but it's something we've discussed. We've got an interest in applying some of the same concepts we have for APIs but in a way that won't compromise performance for high-performance messaging systems.

You're not the only one: http://www.bing.com/search?q=runscope

We'll get there :)

Thanks, you're very kind :)

This comment probably isn't helping with our Google 'Did you mean?' problem ;)

Which appears to be no longer maintained.

requestb.in

The URL scheme you're using makes it really easy to view everyone else's mocks.

If the live server has side effects when making the call (send an email, charge a card, etc) and you just want to test against the response headers/body, it can be very useful. A local mocking library is also good for that, but for quicker tests this is nice.

What do you use for your local testing?

What do you use for your existing tests? VCR?

Before Discourse Sam was at Stack Exchange, which is all .NET/Visual Studio. I assume that's where he's coming from on editor load time.

It's Java, PHP, Python, Ruby AND Objective-C. I think the naming criticisms are fair.

This isn't complete until the shorthand box notation is changed from top, right, bottom, left to top, left, bottom, right.

I don't think the age of the company matters much. Incentives can be aligned/misaligned at any age. I wrote a similar post not that long ago that argues many of the same points (albeit with a more incendiary title) http://thenextweb.com/dd/2013/03/12/apis-are-dead-long-live-...

I think that ship has sailed.

You are more than welcome to (email is my twitter handle in my profile at gmail). However, you should ask them here so everyone can benefit!