WrapAPI
wrapapi.com
- Free plan
- Web
- Browser extension
- API
- Self-hosted
What WrapAPI is
WrapAPI builds APIs on top of existing websites. Its visual Builder starts with requests captured by a Chrome extension, which records browser actions and page loads, filters server requests, and turns selected requests into templates. Users can extract data from HTML, JSON, and XML responses, including when layouts or error cases vary. The Builder can identify changing URL or request-body parts as parameters, and outputs can be defined by selecting elements or writing regular expressions. It supports URLs, query strings, POST data, and file uploads; published endpoints can be called using regular HTTP requests. The interface lists GET, POST, PUT, DELETE, HEAD, OPTIONS, PATCH, and TRACE methods. Its Proxy can capture Android app and webview requests, inspect desktop app requests, and save and replay requests for debugging. WrapAPI is available through API, extension, self-hosted, and web options. The free Community plan includes 30,000 API calls per month, but requires public APIs to be shared with the community and provides support without an SLA.
Who it suits
WrapAPI may suit developers who want to turn website requests and response data into callable endpoints. Its self-hosted option and Proxy tools also fit teams working with app or desktop traffic.
Good to know, and what to watch
- Visual Builder extracts HTML, JSON, and XML data
- Published endpoints accept regular HTTP requests
- Proxy can save and replay requests for debugging
- Self-hosted deployment is available
- Capture extension works only with Chrome
- Community APIs must be shared publicly
- Community support has no SLA
Plans
Every plan and priceBusiness - Cloud
Business - Self-hosted
Fully managed
Community
Free plan
The verdict
WrapAPI provides a visual route from captured website requests to reusable API endpoints, with a free Community plan and self-hosted options. The Chrome-only capture extension and public-sharing requirement on Community are important constraints.
What the maker publishes
- API methods
- The API Builder interface lists GET, POST, PUT, DELETE, HEAD, OPTIONS, PATCH, and TRACE methods. source
- Browser compatibility
- The request capture extension is compatible only with Chrome, while the rest of the site works with any browser. source
- Data collection
- The privacy policy says capture and test case pages collect only requests users specifically save to an API element, while API-use request and response content may be retained in part. source
- Data extraction
- The Builder lets users visually select data and extract from HTML, JSON, and XML responses, with support for multiple layouts and error cases. source
- HTTP requests
- The Builder supports setting URLs, query strings, POST data, and file uploads, and published endpoints can be called with regular HTTP requests. source
- Inputs and outputs
- WrapAPI can identify changing URL or request body parts as parameters and lets users define outputs by selecting elements or writing regular expressions. source
- Maker
- WrapAPI was created by Peter Xu with help from Harry Yu, and the site identifies Myrtlelime Inc. as its operator. source
- Proxy
- WrapAPI Proxy can record Android app and webview requests, inspect desktop app requests, and save and replay requests for debugging. source
- Proxy privacy
- The Proxy page states that request captures are not saved on WrapAPI's server. source
- Purpose
- WrapAPI builds APIs on top of existing websites. source
- Request capture
- Its Chrome extension records browser actions and page loads, filters server requests, and uses requests as API templates. source
- Security
- The privacy policy says WrapAPI uses physical, electronic, and procedural safeguards and limits information access to authorized employees and contractors who need it. source
- Sharing
- Users can share and build on APIs from other WrapAPI members; the Community plan requires APIs to be shared publicly. source
- Support
- The Community plan has support without an SLA; Business plans list support with SLAs, and the docs provide [email protected] for bug reports. source
Checked against the maker's pages on 9 Oct 2026.