Frequently Asked Questions

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.

What is a Beeceptor endpoint?

A Beeceptor endpoint is a dedicated HTTP server that you can configure to return custom responses. Each endpoint comes with its own unique sub-domain, making it easy to:

  • Mock API responses during development and testing
  • Inspect and analyze incoming HTTP requests
  • Route traffic to other servers if needed
To start using it, simply replace the base URL of your service/API in your application code with the Beeceptor endpoint URL. For example, if your endpoint is named my-server, the assigned sub-domain will look like:https://my-server.proxy.beeceptor.com.

How do I set up a mock server in Beeceptor?

Setting up a mock server in Beeceptor is quick and straightforward:

  1. Create a mock server – From the Beeceptor home page, choose a name for your mock server. This generates a unique endpoint URL for you.
  2. Send a request– Use the generated endpoint URL in your application or API client (like Postman or curl) to send a request.
  3. Create a rule – In the Beeceptor dashboard, click "Create Rule" for the captured request.
  4. Define the response – Customize the response by setting the status code, headers, and response body.
  5. Save and test – Once saved, Beeceptor will return your defined response whenever a matching request path is received.
This allows you to simulate API behavior without writing backend code. You can create multiple rules to mock different routes and scenarios.
👉 For more details, see this guide on setting up mocking routes.

What is the Beeceptor dashboard?

The Beeceptor dashboard is a central place where you can view and manage all incoming requests to your endpoint. It lets you:

  • Intercept and review HTTP requests sent to your endpoint
  • Inspect request details such as headers, payload, and query parameters
  • Define and manage mock responses directly from the interface
For example, if your endpoint is my-endpoint.proxy.beeceptor.com, all requests to it can be viewed and analyzed on the dashboard at:https://beeceptor.com/console/my-endpoint. This makes it easy to debug, monitor traffic, and set up mock rules without modifying your application code.
beeceptor dashboard demo

Are the endpoints secure or private?

Free endpoints are public.

  • Anyone having a link to the dashboard can see incoming requests. Copy and share the dashboard URL.
  • On the dashboard, you see the number of online users for that endpoint.

Does Beeceptor support HTTPs?

Yes! Beeceptor supports HTTPs. You can send requests with HTTP and HTTPs, both. In addition, Beeceptor supports HTTP/2 as well.

Does Beeceptor support Cross-Origin Resource Sharing (CORS)?

Beeceptor supports CORS by default. This will ease making a cross-domain request from any webpage.

  • All OPTIONS calls are accepted by default and you don't need to create rules.
  • All the responses contain Access-Control-Allow-Origin: * header making API consumption easier.
Check out the Origin Whitelist documentation to know more about this.

What is 'Proxy Setup'?

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.

How do I simulate and test a 3rd-party API using Beeceptor?

Beeceptor allows you to simulate and test against 3rd-party APIs by acting as a proxy layer between your application and the actual API. Instead of calling the 3rd-party API directly, you point your application to a Beeceptor endpoint that wraps the original API. This approach gives you:

  • Traffic inspection – View and analyze all requests and responses exchanged with the 3rd-party API.
  • Request/response recording – Capture real interactions for debugging or replay.
  • Mocking flexibility– Define rules to override some or all responses. For example, you can simulate error codes, delays, or alternate payloads without depending on the real API.
This is especially useful for scenarios where the 3rd-party API is unreliable, rate-limited, or costly to use during testing.

Can I use Beeceptor for load or performance testing (e.g., 100+ requests/sec)?

Yes, Beeceptor supports high request volumes on paid plans. For load or performance testing scenarios—such as sending 100+ requests per second—the Scale plan is the most suitable option. Please refer to the pricing page to choose a plan that fits your needs. If your requirements exceed what’s offered, feel free to contact our support team for a custom solution.

Can I see the request history for an endpoint or mock server?

Yes, with the Team plan and above. Refer Request History documentation.

How much does Beeceptor cost?

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.

  • Beeceptor is free for public endpoints with a limit on daily requests. Feel free to spread your love and share feedback.
  • Beeceptor comes with awesome features with paid plans. These are private endpoints, request history, sharing with the team, email support, API access, OpenAPI support, etc. Refer to the pricing page for a detailed comparison.

Can I manage mocking routes and rules programmatically using APIs?

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.

What is the privacy policy?

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.

How Beeceptor is different from RequestBin or Mocky.io?

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.

How long does Beeceptor keep HTTP and API request data?

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:

  • Request Storage: All HTTP/API requests sent to the mock endpoint are stored for 10 days. Following this period, the data is automatically purged. This stored information encompasses the request and response payloads, headers, and other relevant details.
  • Application Logs Beeceptor retains application logs for 30 days. These logs serve critical purposes such as auditing, providing support, and monitoring our services. They contain minimal information like request paths, status codes, and source IP addresses. However, it's important to note that application logs do not retain request/response payloads or headers. Furthermore, Personally Identifiable Information (PII) data is never present in these logs, ensuring the utmost protection of sensitive information.

How do I delete all the stored requests on Beeceptor?

Requests sent to Beeceptor are automatically purged 15 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.

What's the procedure for removing an endpoint in Beeceptor?

The process for deleting an endpoint on Beeceptor varies depending on whether you're using a free or paid plan:

  • Free Endpoints:To clean up a free endpoint, simply remove all mocking rules, proxy setups, and other configurations. This makes the endpoint available for others to use. Keep in mind, free endpoints are public and can be reused by anyone. Additionally, free endpoints are automatically deleted after 90 days of inactivity to ensure we can keep offering the free plan and make resources available for new users. This deletion occurs without prior notice.
  • Paid Endpoints:If you have a paid endpoint and wish to delete it, please contact our support team for assistance. Paid endpoints are not deleted as long as the subscription is active. However, if your subscription has been inactive for more than 12 months, we will send you a notification email before cleaning up the endpoint.

How do I delete my account?

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.

Does Beeceptor have a static IP address?

Yes, Beeceptor provides a static IP address for mock servers. This is useful when you need to whitelist Beeceptor’s public IP within your network firewall or security settings. To request the static IP details, please contact our support team.

Can I deploy Beeceptor on my own servers (on-premise)?

Yes, Beeceptor offers an affordable on-premise version that can be deployed on your private servers or within a cloud environment like AWS, Azure, or a VPC. The on-premise build is designed for high security and can even run in air-gapped environments—ensuring that no data leaves your internal network. For pricing and setup details, please get in touch with our support team.

When Should You Use Beeceptor?

Beeceptor is more than just a quick mock server. It’s a contract virtualization and API simulation platform that empowers QA teams, developers, and DevOps engineers to test with confidence even when real services are unavailable, unstable, or costly to invoke.

Common scenarios where Beeceptor adds value:

  • Rapid API Mocking – Stand up a REST API in seconds to validate integrations without backend dependencies.
  • Code-free Fake APIs – Build fully functional test endpoints without writing a single line of backend code.
  • Contract Virtualization – Host your OpenAPI/Swagger specifications and instantly generate mocks to validate contract adherence across teams.
  • Custom Response Simulation – Configure success, error, or edge-case responses to ensure robust error handling in client applications.
  • Performance & Load Testing – Safely simulate high request volumes without burdening downstream or production systems.
  • Latency & Fault Injection – Introduce artificial delays, timeouts, or failures to test retry mechanisms and rarely reached code paths.
  • Local Webhook Tunneling – Expose your local development services to Internet, and receive and inspect webhook payloads during QA.
  • Dynamic Response Behavior – Go beyond static mocks by returning responses based on request payloads or query parameters.
  • Stateful Mocks –Simulate user flows that maintain context (e.g., e-commerce carts items, journeys, wizards, etc) and user state, spanning across multiple API calls.
  • A/B Testing & Version Switching – Seamlessly route traffic between API versions (e.g., sandbox vs production) to compare behaviors.
  • Unblocking Frontend Development – Enable UI and QA teams to test workflows even when backend APIs are incomplete or delayed.
  • Webhook Testing & Inspection – Create temporary endpoints to capture, analyze, and validate webhook integrations.