Reinfluence for developers
Connect the machines you already use.
A small, steady API for card machines, handhelds and your own software. Keys belong to one outlet and do only what you allow.
Create a key
Front counterName
Scopes
- menu:read
- orders:read
- orders:write
- payments:read
- payments:write
Get started
- 1
Create an account
Sign up and add your business. The API belongs to a business, so you need one first.
- 2
Add a device or create a key
In the app open Settings, then Integrations and API. A device is a machine you register. A key is a credential you hold.
- 3
Choose its scopes
Give it only what it needs. You can change your mind and revoke it at any time.
- 4
Open the reference
The full list of calls, with your own address and examples, sits inside the app for the business owner.
Keys and scopes
A key is sent as a bearer token. It belongs to one outlet, and a request outside its scopes is refused with permission_denied. Choose the fewest scopes that do the job.
| Scope | Lets the key | Typical use |
|---|---|---|
| menu:read | Read the menu | Show the menu on a screen, a kiosk or a handheld. |
| orders:read | Read orders | Pull orders into accounting or reporting software. |
| orders:write | Create orders and add items | Start an order from your own app and add to it. |
| payments:read | Read bills waiting for payment | See which bills are waiting to be collected. |
| payments:write | Record payments | Record a payment taken on a card machine or handheld. |
A key is shown once, stored only as a hash and can be revoked. How keys are protected.
Safe retries
Networks drop. Anything that creates something can be sent again without doing the work twice, if you give it your own reference.
- Creating an order
- Send your own reference for it. Send it again and you get the order you already made.
- Adding items
- Give each item its own id. A repeated item is added once.
- Recording a payment
- Send an idempotency key with it. The same key records the payment once, however many times you send it.
- Reading
- Reads can always be repeated. Lists page forward with a cursor.
Money
Amounts are whole numbers in the smallest unit of the currency, so there is no rounding to argue about. Prices always come from the menu, never from the caller.
You send
12550
The customer pays
125.50
Errors
Every failure has the same shape. Branch on the code, show the message, and quote the request id when you contact us.
{
"error": "This API key does not have\n the payments:write scope.",
"code": "permission_denied",
"request_id": "req_5f2c9a1d4b7e"
}invalid_request
A field is missing or wrong. The error says which.
authentication_failed
The key is missing, unknown or revoked.
permission_denied
The key is valid but lacks the scope for this.
not_found
That order, table or item does not exist for this outlet.
conflict
The request clashes with the current state, such as a closed order.
unprocessable_request
The request is well formed but cannot be done, such as paying more than the balance.
rate_limited
Too many requests. The answer says how long to wait.
Limits
- 180
- requests a minute for each key
- 600
- requests a minute for each network address
- 100
- items in one order, and entries in one page
Over the limit, the answer is rate_limited with a Retry-After header.
Tools
Start building with Reinfluence
Create an account, add a device and make your first call today.
