eSLOGLab

DEVELOPER WORKSPACE / TEST PREVIEW

From payment data.
To invoice XML.

Explore eSLOG conversion, check your XML, and connect your app.
A small workspace for the work between payment and invoice.

↳ Stripe · Paddle · Lemon Squeezy◈ eSLOG 2.0
01 / PLAYGROUND

Try the complete flow.

SAME-ORIGIN API

01 Payment data

JSON INPUT
Examples are loaded from the API.JSON
1 credit / conversion

02 Invoice XML

No document loadedEDITABLE · XML
Ready for a check

Separate schema, EN 16931 and signature-integrity results appear here.

This workspace sends invoice data to the server for processing. Recent usage stores operation metadata, not invoice bodies. For a check that stays on your device, use the local validator ↗.

Build with the API / a small integration reference

Use your secret key from a trusted server, never a public browser app. Replace the placeholders below; example data comes from GET /api/examples/stripe.

curl -X POST /api/v1/transform \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: A_NEW_UUID_FOR_THIS_REQUEST' \
  --data @request.json

# Free schema check; no account required
curl -X POST /api/v1/validate/free \
  -H 'Content-Type: application/json' \
  --data '{"xml":"YOUR_XML_HERE"}'

POST /api/v1/validate/extended accepts {"xml":"…"} and needs authentication and an idempotency key. Use a new UUID for a new billed request; reuse it with the same body for a network retry. This playground does that for you.