Skip to main content

Get request history

GET 
/v2/endpoints/:endpoint/requests

Retrieves a paginated, searchable list of HTTP requests received by the mock server. Each request log contains metadata about the incoming request, the generated response, and how Beeceptor processed it.

Purpose​

The Request History API enables:

  • Debugging API integrations by inspecting request/response payloads
  • Auditing API traffic patterns and usage
  • Verifying webhook deliveries and payload contents
  • Analyzing which mock rules matched incoming requests

How Request Logging Works​

When a request arrives at a Beeceptor endpoint, the following information is captured:

  1. Request Metadata: HTTP method, path, timestamp, source IP
  2. Request Details: Headers, body content, HTTP version
  3. Processing Information: Which rule matched (if any), processing time, behavior type
  4. Response Details: Status code, headers, body content
  5. Callout Information: If the request was proxied, details of the upstream request/response

Behavior Types​

Each logged request includes a behavior field indicating how it was processed:

BehaviorDescription
mock-ruleMatched a user-defined mock rule
proxyForwarded to upstream proxy target
calloutTriggered an HTTP callout (sync or async)
grpcProcessed as a gRPC request
wsdlMatched a SOAP/WSDL operation
graphqlProcessed as a GraphQL request
tunnelForwarded to local machine via tunnel
oasGenerated response from OpenAPI specification

Response Modes​

Compact Mode (Default)

Returns basic request information optimized for listing and overview:

  • id, date, method, path, status, timeTaken
  • rule: Whether a rule matched and which rule ID
  • behavior: How the request was processed

Verbose Mode (mode=verbose)

Returns complete request and response details for debugging:

  • All compact mode fields
  • request: Full request body, headers, HTTP version
  • response: Full response body, headers, HTTP version
  • callout: If proxied, includes target request/response details
  • multipartData: Metadata for file uploads (file content available via download endpoint)

Pagination​

Uses cursor-based pagination for efficient traversal of large datasets:

  • Default page size: 20 requests
  • Maximum page size: 100 requests
  • Results are sorted by date descending (newest first)
  • Use the cursor from the response to fetch the next page
  • Continue until pagination.hasMore is false

Filtering Capabilities​

Multiple filters can be combined to narrow down results:

Time-Based Filters:

  • dateFrom / dateTo: ISO 8601 timestamps for absolute date range
  • dateRange: Relative duration (e.g., '1h', '24h', '7d')

Request Filters:

  • method: HTTP method (GET, POST, PUT, DELETE, PATCH)
  • path: Path substring or regex pattern
  • status: Response status code (200-599)
  • requestBody: Search within request body and multipart field names
  • responseBody: Search within response body

Processing Filters:

  • behavior: How the request was handled
  • ruleMatched: Whether a mock rule matched (true/false)
  • isMultipart: Requests with file uploads

Multipart/Form-Data Handling​

For requests containing file uploads:

  • File metadata (field name, file name, content type, size) is included in verbose mode
  • Actual file content is stored separately and available via the download endpoint
  • Search by field name or file name using the requestBody filter

Data Retention​

  • Request history is retained for up to 10 days
  • Older requests are automatically purged
  • Use the DELETE endpoint to manually clean up old requests

Sensitive Data Handling​

If header masking is enabled in endpoint settings:

  • Sensitive headers (Authorization, API keys, etc.) are redacted
  • redacted: true flag indicates data was masked

Request​

Responses​

Request history retrieved successfully. Response format:

  • Without requestId path parameter: Returns paginated array with cursor-based pagination
  • With requestId path parameter: Returns single RequestLog object directly