Okapi

Okapi is an in-browser-browser. Why build a browser inside a browser?

1. To navigate public APIs more easily.
2. To use PUT, DELETE, HEAD, and indeed custom methods, not just GET and POST.
3. To get and set headers more easily.
4. To test your public API against the restrictions of Ajax (like these).

Usage

Use Firefox. It's unreadable in Internet Explorer. Patches welcome if they aren't too complicated.

▼ Headers ▼

These buttons show or hide the 'Headers' tables on either side.

Copy

This button copies the body of the response over to the Request body textbox, so you can edit it and either PUT or POST it back (possibly to a different URI).

Render

Overlays an iframe with the response body rendered inside it.

Installation

Grab okapi.html. Use Subversion if you like. Okapi is a single HTML file which you can serve from any site, statically.

Okapi is now 2 files; the desire for a sexy gradient background overcame my desire for a single file:

• okapi.html
• okapibg.png

Use Subversion if you like.

Here's how to do it in Apache 2:

DocumentRoot /file/path/to/okapi

and CherryPy 3 config:

[/uri/path/to/okapi]
tools.staticdir.on = True
tools.staticdir.dir = "/file/path/to/okapi"