WrapAPI

What WrapAPI is

WrapAPI builds APIs on top of existing websites. Its visual Builder turns captured browser requests and selected response data into endpoints: a Chrome extension records browser actions and page loads, filters server requests, and uses chosen requests as templates. In the Builder, users can select data in HTML, JSON, and XML responses, including across multiple layouts and error cases. It can identify changing URL or request-body parts as parameters, and define outputs through selected elements or regular expressions.

The Builder supports URLs, query strings, POST data, and file uploads. Published endpoints can be called with regular HTTP requests, and its interface lists GET, POST, PUT, DELETE, HEAD, OPTIONS, PATCH, and TRACE methods. WrapAPI also offers a Proxy to record Android app and webview requests, inspect desktop app requests, and save and replay requests for debugging. The site says Proxy captures are not saved on WrapAPI's server. The free Community plan costs nothing and includes 30,000 API calls per month, shared infrastructure, and community support without an SLA; APIs on that plan must be shared publicly. Business options include cloud, self-hosted, and fully managed plans, with private API options and support with SLAs. WrapAPI was created by Peter Xu with help from Harry Yu, and Myrtlelime Inc. is its operator.

Who it suits

WrapAPI suits people who want to build endpoints from requests and data on existing websites, using a visual workflow. The free Community plan may suit users who can work within 30,000 API calls per month and share APIs publicly; private API and self-hosted options are listed in business plans.

Limits

The free Community plan costs nothing and allows 30,000 API calls per month. It requires public APIs to be shared with the community, uses shared infrastructure, and provides support without an SLA.

Getting started

1. Open wrapapi.com in a browser; the site works with any browser.
2. Install and use the Chrome extension to capture browser actions and page loads.
3. Select requests as templates and choose response data in the Builder.
4. Set parameters, outputs, and any URLs, query strings, POST data, or file uploads.
5. Choose a plan; the free Community plan requires public API sharing.
6. Call a published endpoint with a regular HTTP request.

Verdict

Pick WrapAPI if you want a visual way to build APIs on top of existing websites, or need a listed self-hosted option. Look elsewhere if you need the capture extension in a browser other than Chrome, private APIs on the free plan, or Community support with an SLA.