HTTP

Chimera supports a variety of flags to help you customize and control how the mock http API behaves.

Basic Flags

--path <file>

Path to your data.json or schema.json file.

chimera-cli --path ./data.json http

Note

Pass a data.json when you want to serve from it and if you want Chimera to generate the data automatically pass a schema.json. Refer to Data Auto-Generation for Data Auto-Generation

---

--quiet

Run without any log generation

chimera-cli --path data.json --quiet http

Note

By default, logs are genrated in STDOUT and stored in chimera.log.* in a rolling format

• Directoryproject/

  • data.json
  • chimera.log.2025-08-03
  • chimera.log.2025-08-04
  • chimera.log.2025-08-05

---

--port <number>

Specify the port Chimera runs on. Default is 8080.

chimera-cli --path data.json http --port 3000

---

--latency <duration>

Simulate network latency. This simulates a latency of 250ms

chimera-cli --path data.json http --latency 250

---

Pagination

--page <number>

Enable pagination for large datasets. This sets the default number of items per page.

chimera-cli --path data.json http --page 10

---

Sorting

--sort <route> <asc|desc> <attribute_in_route>

Sort a specific route’s array by a key. Example:

chimera-cli --path data.json http --sort api/v2/data asc id

---

Data AutoGeneration

--auto_generate_data

Use a schema definition to generate data.

chimera-cli --path ./schema.json http --auto_generate_data

Refer to Data Auto-Generation for Data Auto-Generation. Use a sample schema.json here

---

Server Behavior

--cors

• Directoryproject/

  • data.json
  • chimera.cors

chimera-cli --path data.json http --cors

CORS is enabled by default (allows all domains). Use this flag to allow only certain domains by adding only the allowed domains in a chimera.cors file. Use this sample chimera.cors here

---

Help

--help

Show all available flags for http.

chimera-cli http --help