Mocklet Documentation Mocklet turns HAR traffic into a live mock server for frontend, QA, and integration testing. This page covers setup, first mock creation, day-to-day workflow, and common troubleshooting steps.
1. Choose Your Start Path Browser Extension Flow Install the Mocklet extension for your browser. Open DevTools and capture API traffic while using your app. Export HAR and create a mock in one flow. Copy the generated mock endpoint into your frontend or tests. Web Upload Flow Open Mocklet Web Upload . Upload a HAR file recorded from your API calls. Review parsing feedback and save a mock configuration. Run the generated endpoint and validate client behavior. 2. Standard Mocking Workflow Capture or upload representative traffic that covers the main success and error paths. Validate HAR structure and remove noisy or sensitive entries before publishing. Tune path matching, query matching, and body matching for predictable responses. Set latency, status overrides, and fallback behavior for resilience tests. Share mock URL with your team and keep mocks short-lived with TTL controls. 3. Primary Actions Validate and Normalize HAR Catch malformed entries early so route matching works consistently across environments.
Configure Dynamic Matching Match by method, path, query params, and optional body rules instead of relying on static fixtures.
Simulate Failures and Latency Emulate timeout, 4XX/5XX, and slow-network scenarios before they appear in production.
Inspect Runtime Behavior Use hit and miss diagnostics to explain why requests match or fail and iterate quickly.
5. FAQ Do I need an extension to start? No. You can use web upload immediately. The extension is useful when you want faster capture loops directly from browser traffic.
Can I upload production HAR data? Do not upload production captures with real secrets or personal data. Use sanitized development traffic.
How long do mocks stay active? Mocks are temporary and can expire automatically based on TTL settings, so stale endpoints do not linger.
6. Troubleshooting If routes do not match, verify request path normalization and query parameter ordering. If response bodies look stale, regenerate mock data from a fresh HAR capture. If upload fails, check HAR size and remove binary payloads you do not need for mocking. If team members see different behavior, align on one mock version and TTL policy. Back to landing Privacy policy Terms of service RapidAPI