Trace Details
Click on any row in the trace list to open the full detail view. This page gives you the complete record of a single communication event — what Mozrest sent to your POS, what your POS returned, and whether it succeeded.
Overview Panels
The top of the trace detail page shows three panels:
Overview
| Field | Description |
|---|---|
| Timestamp | Exact date and time of the communication |
| Type | Flow type (e.g. MOZREST TO POS, POS TO MOZREST) |
| Direction | OUTBOUND (Mozrest sending) or INBOUND (Mozrest receiving) |
| Status Code | HTTP response code (200 = success, 4xx/5xx = error) |
| Duration | Total time for the request/response cycle |
Context
Shows the Venue, RMS, and POS system involved in this trace.
Metadata
Shows the Order ID, Check Number, and Reservation ID associated with the trace. Use these to cross-reference with your POS records.
Request Details
The full API call Mozrest sent to your endpoint (or that your POS sent to Mozrest):
| Field | Description |
|---|---|
| Method | HTTP method (e.g. POST, PUT, GET) |
| URI | The endpoint URL that was called |
| Headers | HTTP headers including authentication tokens and content type |
| Body | The full JSON payload (e.g. table IDs, party size, guest details, prepayment) |
Response Details
What your POS returned:
| Field | Description |
|---|---|
| Status Code | HTTP status code |
| Response Body | The data your endpoint returned |
| Error Details | If failed, the error message is highlighted for easy identification |
Identifying Failures
When a trace fails, the detail view shows:
- The HTTP error code your endpoint returned (e.g. 500, 400, 409)
- The full error message, highlighted in red
- The request payload that caused the error — so you can reproduce and debug locally
Common POS-side failure patterns
| Symptom | What to check |
|---|---|
| Mozrest → POS trace shows 400 | Your endpoint rejected the payload. Check the request body — is a required field missing or malformed? |
| Mozrest → POS trace shows 401/403 | Authentication failed. Verify the Bearer token Mozrest is using matches your configuration. |
| Mozrest → POS trace shows 404 | The endpoint path doesn't exist on your side, or the venue/table ID is not recognised. |
| Mozrest → POS trace shows 409 | Conflict — e.g. trying to create an order on a table that already has one. Check your table/order state. |
| Mozrest → POS trace shows 500 | Unhandled error on your side. Use the request payload to reproduce the issue locally. |
| POS → Mozrest trace shows FAILED | Your webhook to Mozrest failed. Check the response — Mozrest may have rejected the payload due to validation errors. |
| High duration values | Your endpoint is slow to respond. Investigate performance bottlenecks. |
Use Cases
During Integration (Sandbox)
- Verify Mozrest can call your endpoints successfully (Mozrest → POS flow).
- Confirm your responses match the expected format (correct order ID, check number).
- Validate your webhook sends are received by Mozrest (POS → Mozrest flow).
- Test all order lifecycle operations: create → update → close / void.
- Debug failures before accreditation — no need to contact Mozrest for logs.
In Production
- Monitor ongoing endpoint health and response times.
- Quickly trace a specific order when a venue reports an issue.
- Determine whether a failure occurred on your side or Mozrest's side.
- Gather trace evidence when collaborating with Mozrest support.