How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Beeceptor Mock Rules API

The Mock Rules API from Beeceptor — 4 operation(s) for mock rules.

Beeceptor Mock Rules API is one of 5 APIs that Beeceptor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Mock Rules. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 4 paths, and defines 21 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.

Requests are made against a single base URL, https://api.beeceptor.com/api.

10 operations 4 paths 21 schemas 2 DELETE2 GET1 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Server
https://api.beeceptor.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Beeceptor Mock Rules API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth).

Paths & Operations 10

Across 4 paths, the API surfaces 10 operations — 2 DELETE, 2 GET, 1 PATCH, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Mock Rules 10
GET
/v2/endpoints/{endpoint}/rules
Get all rules
1 param → 200401403404
POST
/v2/endpoints/{endpoint}/rules
Create a new rule
1 param body → 201403404500
PUT
/v2/endpoints/{endpoint}/rules
Bulk replace all rules
1 param body → 200400401
DELETE
/v2/endpoints/{endpoint}/rules
Delete all rules
1 param → 200401
POST
/v2/endpoints/{endpoint}/rules/reorder
Reorder rules
1 param body → 200400401404500
GET
/v2/endpoints/{endpoint}/rules/{ruleId}
Get a single rule
2 params → 200401404
PUT
/v2/endpoints/{endpoint}/rules/{ruleId}
Update a rule (full replacement)
2 params body → 200400401404
PATCH
/v2/endpoints/{endpoint}/rules/{ruleId}
Update a rule (partial)
2 params body → 200400401404
DELETE
/v2/endpoints/{endpoint}/rules/{ruleId}
Delete a rule
2 params → 200401404
POST
/v2/endpoints/{endpoint}/blobs
Upload a blob file
1 param body → 201400401403404500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are GrpcAction (8 properties), WeightedResponse (7 properties), CalloutAction (7 properties), MockAction (5 properties). Each schema is shown below with its type and property counts.

CrudAction
object
Enables stateful CRUD behavior for a resource path. Beeceptor will automatically handle POST (Create), GET (Read), PUT (Update), and DELETE operations for JSON…
2 properties 2 required
CalloutAction
object
Triggers an external HTTP request (Callout) when the rule matches. This is useful for proxying traffic, transforming payloads, or notifying webhooks.
7 properties 3 required
GrpcResponse
object
2 properties
BodyCondition
Performs a search or pattern match against the raw HTTP request body.
RuleWithId
A Rule object that includes a unique identifier, typically returned in responses.
WeightedAction
object
Distributes incoming requests across multiple responses based on assigned weights. The combined weights of all responses must equal exactly 100.
2 properties 2 required
Rule
object
A Rule defines the behavior for an incoming request. It consists of a set of conditions and a resulting action. Beeceptor matches requests against rules in the…
5 properties 3 required
Condition
Error
object
Standard error response structure.
1 property
PathCondition
GraphQLCondition
Matches against incoming GraphQL queries. Beeceptor parses the GraphQL operation name or query structure to determine a match.
SoapActionCondition
Targets SOAP-based web services by matching against the 'SOAPAction' header.
GrpcMethodCondition
Primary condition for gRPC rules. Matches the full gRPC method path (e.g., 'package.Service/MethodName').
Action
StateCondition
Matches against persistent state variables (Counters, Data Stores, or Lists) stored in your endpoint. This allows for stateful mock transitions.
HeaderCondition
Inspects the value of a specific HTTP header in the incoming request.
GrpcAction
object
Defines the mock behavior for gRPC calls, supporting unary and streaming communication.
8 properties 3 required
BaseCondition
object
1 property 1 required
MockAction
object
Returns a predefined HTTP response to the caller.
5 properties 3 required
BodyParamCondition
Matches against parsed body parameters. This is applicable for JSON payloads, XML, or Form-Data where Beeceptor can extract named fields.
WeightedResponse
object
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

beeceptor-mock-rules-api-openapi.yml Raw ↑

Other APIs Beeceptor publishes across the network.

Beeceptor API
Beeceptor Endpoint Settings API
Beeceptor Request History API
Beeceptor State Store API
Where this information came from

This is an independent, third-party profile of Beeceptor Mock Rules API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.