Overview
Everything you need to start integrating Platon.
What is Platon?
Platon is the Limpidius REST API for emitting structured digital receipts from point-of-sale transactions. You send a single request containing the transaction details (product lines, VAT breakdown, payment method) and Platon handles receipt generation and delivery to your customer.
Platon supports the following delivery modes:
- Email: the receipt is sent directly to the customer's inbox.
- Print: a paper receipt is generated at the POS terminal.
- Email and print: both channels are used simultaneously.
- No print: the transaction is recorded without any delivery.
Authentication
All requests must include a valid Bearer token in the Authorization header.
See Authentication
for details on how to obtain a token.
# Include this header with every request
Authorization: Bearer {YOUR_ACCESS_TOKEN}HTTP status codes
| Code | Meaning |
|---|---|
201 Created | The request was accepted and the transaction was processed successfully. |
400 Bad Request | The request body is malformed or missing required fields. |
401 Unauthorized | The provided token is missing, invalid, or expired. |
422 Unprocessable Entity | The request is well-formed but contains invalid values. |
429 Too Many Requests | You have exceeded the rate limit for your API call. |
500 Internal Server Error | An unexpected error occurred on our side. Please retry with exponential backoff. |
Idempotency
The requestId field (UUID v4) is required on every transaction request.
If the same requestId is submitted more than once, only the first request
is processed: subsequent duplicates are silently ignored. This allows you to safely
retry failed requests without risk of double-processing a transaction.
Generate a fresh UUID v4 for every new transaction. Reuse the same UUID only when retrying the exact same request.