Mocko Cloud

Request Logs

The Logs view shows the requests that reach your project as they happen. When a client is not getting the response you expected, this is where you find out what it actually sent.

What you see

Each entry is one request that arrived at your public host. Opening it shows the details you need to tell an intended call from a malformed one:

• The method and path that was requested.
• The request headers, including the ones the client set for you.
• The request body, so you can confirm the payload is what you expect.

Logs stream in live, so you can leave the view open, trigger the call from your app or a curl, and watch it appear.

Why it helps

Most integration confusion comes down to a mismatch between what a client thinks it is sending and what it sends. Logs remove the guessing:

• Confirm a request is even reaching Mocko, rather than being blocked before it leaves the client.
• Check that a header or query parameter your matching depends on is actually present.
• Inspect the exact body a form or SDK produces before you write a mock to answer it.