Question 1

How do I simulate API delays with DeepfakeHTTP?

Accepted Answer

Use the X-Delay header in your dump files to add delays in milliseconds. For example, adding 'X-Delay: 2000' to a response simulates a 2-second delay, helping test client timeouts or loading states.

Question 2

DeepfakeHTTP vs JSON Server: which is better for mocking REST APIs?

Accepted Answer

DeepfakeHTTP is ideal for zero-configuration, dependency-free mocking with OpenAPI support, while JSON Server is Node.js-based and better for simple CRUD mocks with a fake database. Choose based on your need for minimal setup vs. ease with Node ecosystems.

Question 3

Can I use DeepfakeHTTP to mock GraphQL APIs?

Accepted Answer

Yes, it can mock any HTTP-based API, including GraphQL, by defining request-response pairs in dump files. Use templates and wildcards for flexible query matching, as shown in the features list.

Question 4

How to handle authentication in mocked APIs with DeepfakeHTTP?

Accepted Answer

Define request headers in dump files to simulate tokens or credentials. For dynamic validation, use JavaScript handlers to check headers and return appropriate responses, leveraging the request object parameters.

Question 5

Is there a way to import existing API specs into DeepfakeHTTP?

Accepted Answer

Not directly, but you can use the --print-openapi command to generate OpenAPI specs from dumps and manually create dump files from other tools. Integration requires custom scripting or manual conversion.

Question 6

How to persist data between requests in DeepfakeHTTP?

Accepted Answer

Use the --db option with a JSON/YAML/CSV file to populate templates, and JavaScript handlers to modify this persistent data. This allows stateful interactions, such as updating user records across multiple requests.

DeepfakeHTTP

What is DeepfakeHTTP?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions