For feedback, questions, or feature requests, please feel free to reach out to us through our feedback page. Additionally, we have a compilation of frequently asked questions about Beeceptor to assist you further.
A Beeceptor endpoint is a specialized HTTP server configured to send customized HTTP responses. It operates through a unique sub-domain, facilitating mock API server, HTTP traffic analysis, and request routing to different servers.
To utilize it, replace the base URL of your HTTP/API server in your code with the Beeceptor endpoint URL. Each endpoint is assigned a dedicated sub-domain, formatted as my-server.proxy.beeceptor.com..
To create a mock server in Beeceptor, simply provide a name for the server from the home page. Mocking rules can then be added to specify the desired responses for specific routes. When a request path matches a rule, Beeceptor will send the pre-defined response. To begin, send a request and click "Create Rule" to set up the response. Beeceptor automatically captures the request details, allowing customization of the response with status codes, headers, and bodies. Creating a mock server and defining mocking rules is a quick and easy process with Beeceptor. Check out setting up mocking routes to know more about this.
A dashboard is a place where you can intercept and review all incoming requests coming to an endpoint. The Beeceptor dashboard allows you to inspect HTTP payload and set up mocks. When request to my-endpoint.proxy.beeceptor.com, the request & responses are visible on the dashboard page beeceptor.com/console/my-endpoint to inspect the payloads.
Free endpoints are public.
Yes! Beeceptor supports HTTPs. You can send requests with HTTP and HTTPs, both. In addition, Beeceptor supports HTTP/2 as well.
Beeceptor supports CORS by default. This will ease making a cross-domain request from any webpage.
Access-Control-Allow-Origin: * header making API consumption easier.Beeceptor's proxy configuration functions as an advanced man-in-the-middle (MITM) mechanism, enabling intricate control over API traffic for integration and testing. It routes requests to a designated target domain, with responses from this domain being transmitted back through Beeceptor. This setup is pivotal in monitoring and modifying API interactions in real-time, thus significantly enhancing debugging and testing capabilities. Check out the HTTP Proxy Mode documentation to know more about this.
Beeceptor is an advanced MITM proxy that elevates your API mocking and integration capabilities. If you're utilizing a 3rd party API, you can wrap its endpoint with Beeceptor's sub-domain to gain complete control over the traffic that passes through it. This grants you the ability to easily review all the HTTP communication and record it. Further, you can build mock rules for some or all requests giving you unparalleled flexibility while testing your application.
Yes, with paid plans. Refer pricing page to find a suitable plan and upgrade. Feel free to reach out to us if your requirements are beyond this.
Yes, with the Team plan and above. Refer Request History documentation.
Beeceptor serves as a cloud-based HTTP server, allowing you to tailor responses as needed. Its instant deployment feature enhances your ability to test, experiment, and debug, while also managing request routing efficiently.
Yes, Beeceptor's APIs allow you to programmatically create, update, and manage mocking rules and routes. Additionally, you can retrieve request histories, enabling seamless integration with Continuous Integration (CI) and Integration Tests. For more comprehensive guidance and detailed instructions on using these APIs, please refer to Beeceptor's API Documentation page.
For comprehensive details, please refer to Privacy Policy here. Beeceptor, designed for HTTP request and response inspection, emphasizes privacy and data security in its operations. While it stores endpoint details and the request's content (including URLs, headers, and payloads, etc) security measures are in place. Users are cautioned against transmitting sensitive data like production secrets or API keys through free endpoints. For enhanced privacy, paid plans offer private endpoints, and users are recommended to use unique endpoint names and HTTP headers for additional security validation by Beeceptor.
RequestBin helps by letting us inspect what the client is sending, and Mocky.io creates dummy endpoints to send mocked responses.
Beeceptor covers both in one tool letting you inspect requests and build mock responses.
In addition, Beeceptor has more features to be your one-stop API development companion.
Beeceptor adheres to a well-defined data retention policy, carefully balancing operational requirements with a commitment to data privacy. Here's what you need to know:
Requests sent to Beeceptor are automatically purged 10 days after their receipt. However, if you need to clear them earlier, Beeceptor offers an API feature for this. With an active Team plan or higher, you can use a DELETE API call to trigger an immediate purge of all stored requests.
The process for deleting an endpoint on Beeceptor varies depending on whether you're using a free or paid plan:
Deleting your Beeceptor account is straightforward. After logging in, simply navigate to the 'Edit Account' page where you'll find the option to delete your account. Check this guide to delete your account.