Mocko

Mocko Docs

Dynamic HTTP mocking

Mocko Cloud

Projects and URLs

A project is the unit you work in on Mocko Cloud. It owns a public host, its own mocks and flags, its own request logs, and its own members. Understanding the project is understanding the platform.

One project, one host

Each project answers on a single HTTPS host derived from its slug:

$https://<slug>.free.mockoapp.net

Every request to that host is routed to that project and only that project. There is no path prefix to remember and no shared namespace: a GET /users against your host hits your /users mock. Because the host is a real HTTPS address, you point a client at it exactly as you would point at the upstream service you are standing in for.

The slug is chosen when the project is created and can be changed later from the project settings. Changing it changes the public host, so update any clients that were using the old address.

Switching between projects

You can own several projects at once, for example one per service or one per environment. The control panel always acts on the currently selected project, and the project switcher changes which one that is. Mocks, flags, and logs are all scoped to the selection, so switching projects gives you a clean, unrelated workspace.

Proxying to a real backend

A project does not have to mock everything. Each one has an optional proxy URL: when a request arrives that no mock matches, Mocko forwards it to that address and returns the real response. Leave it blank and unmatched requests simply return a not-found response.

This is what makes a project a selective layer rather than an all or nothing replacement. You mock the endpoints that are unfinished or hard to reproduce, and let everything else fall through to the genuine service:

  • Mock POST /checkout to force a specific failure, while real GET /products requests reach your staging API.
  • Stand your Cloud host in front of a partner API and override only the one endpoint that is not ready yet.
Matching and fall-through behave the same as they do everywhere in Mocko. If you want the full picture of how a request is resolved before it reaches the proxy, read How Matching Works and Proxying and Hosts.

Next

Once traffic is flowing to a project, watch it live in Request Logs, or invite the rest of your team from Team Members.