LPXServer Dump
Pastebin

Dumps live
24 hours

Upload a dump from the LPX anti-crasher, get back a link and an access key. The link shows the viewer; the key unlocks the data. Both stop working once the dump expires.
Nothing is listed publicly. Keys are checked server-side and never stored in clear.
Upload a dump
curl -X POST http://localhost:8080/api/v1/dumps \
  -H "Content-Type: application/json" \
  --data @dump.json
Response
{
  "id": "k4q7x2m9pd1s",
  "key": "LPX-7F3C-91A4",
  "url": "http://localhost:8080/d/k4q7x2m9pd1s",
  "apiUrl": "http://localhost:8080/api/v1/dumps/k4q7x2m9pd1s",
  "createdAt": "2026-09-05T14:23:12Z",
  "expiresAt": "2026-09-06T14:23:12Z"
}
Read it back
Browser
Open url, enter key.
Script
GET apiUrl with header X-Dump-Key: <key>
Metadata
GET apiUrl/meta · public, returns only created and expiry times
Wrong key
403 · ten misses within ten minutes lock the client out (429)
Upload limit
10 uploads per 5 minutes per client, rejected ones included · 429 with Retry-After
Wrong structure
400 · errors lists every offending path
Expired or unknown
404
Payload
Shape
One JSON object. Recognised sections: lpx, server, system, plugins[], players[], log, packetDump, logDate. At least one section is required, types are checked, unknown fields are rejected.
Text fields
log and packetDump take raw text exactly as LPX writes it, or an array of lines.
LPX Pastebin · see README.md for the full API