Category: Web Development Tools
This tool simplifies API testing and sending requests online. The application sends GET or POST HTTP requests to a specified API end-point. The application saves request parameters and results so that you can share them. To activate your personal url, just send a request and a new url will be generated for you.
This tool is an HTTP Client. It is useful for people who want to execute GET or POST requests against an HTTP endpoint. POST requests can be sent as key-value url encoded pairs or as a raw string. If you combine the latter with the appropriate "Content-Type" header you can send "JSON" or "XML" in the POST payload.
Yes you can. The "local" requests will be sent directly from the browser. In order to avoid CORS (cross origin) issues you will need to accept the codepunker.com domain as an authorized sender to your local server. To do that, you can add the following headers in your application:
Access-Control-Allow-Origin: https://www.codepunker.com Access-Control-Allow-Headers: * Access-Control-Allow-Method: *
Because my website runs on https your local domain will need to run on https too - otherwise your local requests will fail because of mixed content. An alternative to this would be to run your local site on 127.0.0.1 which will be considered safe by most browsers.
Once logged in, your saved requests will be automatically grouped by url. This way all queries to
example.com/* will be grouped and they can be named for easy access. For people that are not logged in, the most recent requests are saved using your browser local storage. People that are not logged in must pass the captcha validation to send requests.
After executing the request the application will parse your query and data and create a cURL command that can be copied and executed from the command line.
Saved requests can be monitored. Every 5 minutes, my servers will hit the saved endpoint with a simple get request or with the same parameters that you've defined and will report back if the response status code is anything other than 200 Success.
Your entire requests history can be accessed when logged in and you can track performance over time with charts that display response times and status codes.
There is a hard limit of 240 requests per day per endpoint and IP Address. In other words one IP address can only send 240 requests per day to example.com.