Input Logs (Traffic/Audit)
Overview
The Input Log (also called Traffic or Audit) allows developers and administrators to track calls made to the platform’s APIs.
You can access it at: Partner's Portal > Traffic
This feature provides visibility into requests, responses, headers, 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 Date | UTC time of the call |
| Path | Endpoint called (e.g., /v1/requests/{id}/items/approvers) |
| Method | Operation type (GET, POST, PUT, DELETE) |
| Correlation ID | Unique identifier to track the request end-to-end |
| Response Status | Returned HTTP code (200, 404, 500, etc.) |
2. Request Details
When expanding a row, a panel with Request and Response is displayed.
Request Tab
Shows the data sent to the server:
| Field | Description |
|---|---|
x-me-tenant-id | Tenant identifier |
authorization | Authentication token (masked) |
postman-token | Client tracking token |
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 |
| Full Endpoint | Path + query parameters (e.g., ?pageNumber=1&pageSize=10) |
Response Tab
Shows the data returned by the server:
| Field | 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 Time | Total response time (e.g., 33.7s) |
| Response Size | Response size in bytes |
| Response Body | Body returned by the API (error messages, payloads, data) |
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.