Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/PDNMX/s1_backend/llms.txt

Use this file to discover all available pages before exploring further.

The /v1/logger endpoint allows front-end applications to forward log events to the server so that they appear in the server-side log stream managed by log4js. This is useful when client-side errors or important user actions need to be captured alongside server logs for unified observability. Each entry in the request array is dispatched to the appropriate log4js method based on its level field. Currently supported severity levels are "error" and "info". Any unrecognised level values fall through to logger.info().

​
Endpoint

POST /v1/logger
Content-Type: application/json

​
Request Body

​
logs
array
required
An array of log event objects to be written to the server-side log stream. Each object in the array must include a level field. All other fields present in the object are logged as-is alongside the level.

​
Example Request

curl -X POST http://localhost:3101/v1/logger \
  -H "Content-Type: application/json" \
  -d '{
    "logs": [
      { "level": "error", "message": "Failed to load resource", "url": "/v1/search" },
      { "level": "info", "message": "User performed search", "supplier_id": "EDOMEX" }
    ]
  }'

​
Response

Always returns HTTP 200 OK with a fixed confirmation object once all log entries have been written.
Response
{
  "msj": "ok"
}
​
msj
string
Confirmation string. Always "ok".
Unrecognised level values (anything other than "error" or "info") fall through to logger.info() — they are never silently dropped. Individual log entries do not cause the request to fail; the endpoint always returns 200 OK with {"msj": "ok"} as long as the logs array is present and iterable.

Build docs developers (and LLMs) love

Get started for freeTalk to us