Read recent console output
The server's recent console lines, without holding a websocket open. The cheap answer to "what did it just print?" for a health check or an alert handler.
This is not the file tail, and the difference decides which you want. These are the container's recent stdout, capped by the node and not resumable — consecutive calls overlap, and lines written between them can be missed entirely. The tail follows a file by byte offset and resumes exactly. Durable log shipping wants the tail (see the socket endpoint); this is for a glance.
An empty lines array is a real answer — the container has printed
nothing — and is deliberately distinct from the 502 that means the node
did not reply.
Authorization
orgApiKey game-servers.readAn organisation API key, prefixed tbk_. Create one under
Organisation to API keys; the plaintext is shown once.
The scopes listed on each operation are the abilities the key must carry. They are not OAuth scopes and are not negotiated per request.
In: header
Scope: game-servers.read
Path Parameters
The server's UUID, as returned by the list endpoint.
uuidQuery Parameters
How many lines to ask for. The node clamps this to its own ceiling,
so returned may be lower than you asked for — and lower again on a
container that has not printed that much yet.
1 <= value <= 1000100Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/game-servers/497f6eca-6276-4993-bfeb-53cbbbba6f08/logs"{ "data": { "lines": [ "string" ], "returned": 0 }}