If you have feedback, questions or feature-ask, feel free to write us via feedback page. Here are a few FAQs about Beeceptor.
A Beeceptor endpoint is a mock server, or a sub-domain to serve as an API server base URL.
These endpoints are public just like the real API endpoints. Anyone with the URL can send requests, anyone having a link to the dashboard can view requests and responses in real time. Each endpoint gets a dedicated sub-domain as
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 you can intercept and review all incoming requests coming to an endpoint. Beeceptor dashboard gives you an opportunity to inspect HTTP payload and setup mocks. When you make a request to
my-endpoint.proxy.beeceptor.com, 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 out making a cross-domain call from a webpage. (1) All OPTIONS calls are accepted. (2) Any mock/rules you create, Beeceptor adds a response header
Access-Control-Allow-Origin: * making API consumption easier.
Proxy Setup helps you route requests to a target domain. You can create mock rules to manipulate specific requests instead of sending to the target domain. For example, you can create a rule matching HTTP's
GET method and request path
/my/api/path and send a 403 status code instead of 200 which the target domain would have sent.
Beeceptor is an advanced MITM proxy that elevates your API mocking and integrations 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. 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. Refer Request History documentation.
Yes. You can use Beeceptor APIs to create/update mocking rules. In addition, you can retrieve request history. Using this you can integrate Beeceptor to CI and Integration Tests. Refer to the API Documentation page.
Beeceptor is a request interceptor and a router.
At Beeceptor, we have a structured data retention policy to ensure a balance between operational needs and data privacy. Here's what you need to know:
There is no self-service way to delete endpoints. These are cleaned up after a certain period of non-usage.
You can delete your account with Beeceptor. Once you are logged in, visit the 'Edit Account' page to delete your account.
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.