📄️ Outlets and Acting User
Two headers tell Mekari POS where a request works and who does it.
📄️ Errors
Error Response
📄️ Pagination
List endpoints return one page at a time:
📄️ Idempotency
A network error can hide whether a write succeeded. Send an Idempotency-Key header so that a retry returns the first result instead of creating a second record.
📄️ Rate Limits
Mekari API Gateway limits how many requests a merchant's integrations can send.
📄️ Data Formats
Requests and Responses
📄️ Versioning & Changelog
Versioning
📄️ Approvals
Some outlets ask a manager to approve a return, a refund or an exchange. The manager proves it with a PIN or a one-time code. You then send the approval_token you got with the return, refund or exchange. See Returns, Refunds and Exchanges.
📄️ Returns, Refunds and Exchanges
You can take goods back (return), give money back without goods (refund), or take goods back and sell others in one step (exchange), for any paid order of the outlet.
📄️ Creating Orders
Your application can send paid delivery, takeaway and pickup orders to a merchant's outlet. Mekari POS prices the order, records it with its payments, and puts a ticket on the outlet's kitchen board. Your customer has already paid in your application, so these orders are never open or unpaid.