Traffic
Overview
The Traffic screen (formerly called Input Log or Audit) allows developers and administrators to track calls made to the platform’s APIs.
You can access it at: Partner's Portal > Monitoring > Traffic.
This feature provides visibility into requests, responses, headers, bodies, response times, and status codes.
⚠️ Attention:
This feature is intended for auditing and monitoring purposes. It should not be used as a transactional mechanism or a persistent data source.
Retention and Limitations
- Log retention: 90 days.
- Persistence: not guaranteed for 100% of calls (network failures and downtime may impact).
- Purpose: use for auditing, debugging, and support. Not recommended for critical integrations.
Applications that require full persistence are recommended to implement their own logging mechanisms.
Dashboard Structure
1. Request List
On the main Traffic screen, each row corresponds to a request. Available fields:
| Field | Description |
|---|---|
| Request Timestamp | Date and time of the call, shown in your browser's time zone |
| Path | Endpoint called (e.g., /v1/requests/{id}/items/approvers) |
| Method | Operation type (GET, POST, PUT, DELETE, PATCH) |
| Correlation Id | Unique identifier to track the request end-to-end |
| Response Status | Returned HTTP code (200, 404, 500, etc.) |
The list is paginated (25, 50, or 100 items per page) and can be sorted by the Request Timestamp, Path, Method, and Response Status columns.
Filters
The following filters are available above the list:
- Date: predefined periods (from Last 24 hours to Last 12 months), All period, or Specific period (a range of up to 1 year).
- Status: All, Success (status below 300), Warning (300 to 499), or Error (500 or higher).
- Method: All,
GET,POST,PUT,DELETE, orPATCH. - Search: text search and criteria on the Request Timestamp, Response Status, Path, Correlation ID, and Method fields. Criteria can be saved as filters (saved filters are stored in your browser).
2. Request Details
Clicking a row expands it and shows the Request and Response tabs.
Request Tab
Shows the data sent to the server:
| Field | Description |
|---|---|
| Headers | All headers received in the request. The value of the authorization header is always masked (********) |
| Endpoint | Path + query parameters (e.g., ?pageNumber=1&pageSize=10) |
| Request Size | Request size (in bytes, KB, or MB), when available |
| Request Body | Body sent in the request (formatted JSON), when present |
Examples of headers that usually appear:
| Header | Description |
|---|---|
x-me-tenant-id | Tenant identifier |
authorization | Authentication token (masked) |
x-me-correlation-id | Correlation ID |
host | API host |
user-agent | Request agent (e.g., PostmanRuntime, libs, apps) |
cache-control | Cache policy |
accept | Accepted types |
accept-encoding | Accepted compression |
Response Tab
Shows the data returned by the server:
| Field | Description |
|---|---|
| Headers | All headers returned in the response |
| Response Time | Total response time, in seconds (e.g., 33.7s) |
| Response Size | Response size (in bytes, KB, or MB), when available |
| Response Body | Body returned by the API (formatted JSON: error messages, payloads, data), when present |
Examples of response headers that usually appear:
| Header | Description |
|---|---|
content-type | Response format (e.g., application/problem+json) |
server | Server identifier |
transfer-encoding | Whether chunked or not |
date | Date/time of the response |
connection | Connection state |
ratelimit-limit | Maximum allowed calls |
ratelimit-remaining | Remaining calls in the period |
ratelimit-reset | Time in seconds until the limit window resets |
Response Examples
500 Error (Internal Server Error)
{
"type": "https://datatracker.ietf.org/doc/html/rfc7231#section-6.6.1",
"title": "An error occurred while processing your request.",
"status": 500,
"detail": "An unexpected error has occurred. Please try again later or contact support if the issue persists."
}404 Error (Not Found)
- Indicates that the requested resource does not exist (e.g., nonexistent user or item).
200 Success (OK)
- Indicates that the request was successfully processed, with a payload returned in the Response Body.
Best Practices
- Use the Correlation ID when opening support tickets.
- Monitor spikes of 500 errors and rate limit excesses as integration health indicators.
- If you need to audit beyond 90 days, configure a log export pipeline for your own storage.
- Use status codes and error messages as the first troubleshooting layer.