Logs API

Send structured log events. Requires a logs key. Accepts one event, an array, or { "logs": [...] } (batch up to 100).

Fields

Request

curl -X POST https://manage.vecto3d.dev/api/v1/logs \
  -H "Authorization: Bearer mng_your_logs_key" \
  -H "Content-Type: application/json" \
  -d '{"level":"info","name":"player.join","message":"Vextro joined","metadata":{"slot":12},"traceId":"sess-1"}'

Datasets

Datasets are separate named streams of logs, created on the Datasetspage. A dataset can be restricted so only chosen members can read it (owners and admins always can) — that controls who can read it in the dashboard; sending is governed by holding the key.

Logs go to the defaultdataset unless you say otherwise, so you don't have to change anything to keep using logs as before. To target another dataset, set dataseton an entry, or at the top level to apply it to the whole batch. A per-entry value wins, so one request can carry several datasets. Unknown names are rejected with a 400 rather than being created, so a typo can't quietly make a junk dataset.

# one entry into "police"
curl -X POST https://manage.vecto3d.dev/api/v1/logs \
  -H "Authorization: Bearer mng_your_logs_key" \
  -H "Content-Type: application/json" \
  -d '{"dataset":"police","name":"evidence.saved","message":"Cam footage stored"}'

# a batch into "economy", with one entry overriding to "police"
curl -X POST https://manage.vecto3d.dev/api/v1/logs \
  -H "Authorization: Bearer mng_your_logs_key" \
  -H "Content-Type: application/json" \
  -d '{"dataset":"economy","logs":[{"name":"shop.sale"},{"name":"evidence.saved","dataset":"police"}]}'

Response

{ "count": 1 }

Errors

Errors that aren't from the API

Requests pass through a CDN edge before reaching Manage. If the edge rejects one, you get an HTML error page instead of our usual JSON. That's the quickest way to tell the two apart: if the body isn't JSON, the request never reached us, and it won't appear in your logs.