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 one more capability - proxing. It routes the traffic to original Rest API when needed.

What is an endpoint?

An endpoint is a sub-domain to serve as an API endpoint. These endpoints are public just like the real API endpoints. Anyone with the URL can send requests, anyone having link to the dashboard can view requests and responses. Each endpoint gets a dedicated sub-domain as my-endpoint.proxy.beeceptor.com.

How to setup mocking?

Rules help you send canned/pre-defined responses when a request path matches. You can get started by sending a request and then clicking 'Create Rule'.

What is a dashboard?

Dashboard is a place you can intercept and review requests. Beeceptor acts as a router. 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.

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

Yes, out of the box. (1) All OPTIONS calls are accepted. (2) Any mock/rules you create, Beeceptor adds a response headers Access-Control-Allow-Origin: * making life easier.

How can I use 'Proxy Setup'?

Proxy Setup helps you route request to target domain. Defining rules helps to mock specific requests instead of sending to target domain. For example, you can create a rule matching HTTP's GET method and request path /my/api/path and send 200 status code.

  1. When the rules are enabled, they are matched in shown order and the first match is considered. If no rule is matched, target endpoint is hit as usual.
  2. When the rules are disabled or no rule matches, the endpoint routes the request to target endpoint.

Are the endpoints secure or private?

Free endpoints are public.

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

Can I use this for load/performance testing? (i.e. 100+ requests/sec)

Yes, with paid plans. Refer pricing page to find a suitable upgrade plan.

Is there a HTTPs support?

Yes! We support HTTPs Everywhere. Any endpoint that you create support HTTPs and HTTP both.

Can I see request history for an endpoint?

Yes, with Team plan. Refer pricing.

I want to use this on UI page hosted over HTTPs.

It works! Beeceptor supports HTTPs as well as CORS. This will ease out making an cross-domain call from your webpage.

How much does it cost?

Beeceptor is free for public endpoints with a limit on daily requests. Feel free to spread your love and share feedback. We give awesome features for paid plans. (e.g private endpoints, request history, support, APIs, etc.)

What about privacy?

Beeceptor is a request interceptor and a router. If the dashboard page is open, these are sent over web-socket to inspect. Anyone with dashboard page open can view and inspect request and response payloads. The server persists information about the endpoint (like settings, rules, etc) and requests (like target url, headers and payloads of requests and responses, no. of hits to an endpoint, etc).

Note: You are advised not to send production secrets, passwords or api-keys in any of these: headers/body/payload/url

Use-cases

  • Mock a rest API in seconds.
  • Build a fake API without any coding.
  • Customizable responses to simulate API response and failures.
  • Use this for load testing an API, without load testing the downstream APIs.
  • Simulate latencies and timeouts of downstream APIs (validate rarely reachable code paths)
  • A/B testing by switching API endpoints or versions without any redeployment. (prod code vs new code)
  • Don't block your UI devs when backend APIs are still in development. Just mock it!
  • Create endpoints for web-hooks and inspect incoming payloads.