PulseGrid gives operators of kiosks, EFT terminals, vending machines, and EV chargers a single real-time view of revenue, uptime, and errors — across every location, through a simple REST API.
Locations and terminals on the left, revenue and a live event feed on the right — all floating over a map that updates as your devices report in.
One login for revenue, uptime, errors, products, and your team — no spreadsheets, no stitching together three vendor portals.
No SDK, no gateway, no agent on the box. Whatever runs on the machine posts a small JSON event over HTTPS — and it's on your dashboard within seconds. There are only three things a device ever sends:
POST /events/heartbeatPOST /events/transactionPOST /events/error$ curl -X POST https://pulse-grid.dev/api/v1/events/transaction \
-H "X-Api-Key: pk_live_..." \
-H "Content-Type: application/json" \
-d '{
"amount": 6.50,
"currency": "EUR",
"status": "Success",
"paymentType": "card",
"productName": "Premium wash",
"occurredAt": "2026-07-22T14:05:11Z"
}'
# ✓ stored — on your live feed within secondsDifferent devices, same problem: knowing which one stopped earning, and when.
Something else entirely? If your device can make an HTTPS request, it can report to PulseGrid — start with the integration guide.
POST /terminals/bulkPOST /events/transactionapp.pulse-grid.devPulseGrid is a monitoring and reporting layer. It sits alongside your payment and device stacks; it doesn't try to replace them. Knowing the line up front is what keeps it trustworthy.
A real-time monitoring and reporting layer for unattended devices. It gives you one dashboard for revenue, uptime, and errors across kiosks, EFT/POS terminals, vending machines, and EV chargers. It reads the events your devices send — it does not process payments or control the hardware.
Anything that can make an HTTPS request can post events to the REST API — kiosks, vending machines, EFT/POS terminals, and more. EV chargers connect over OCPP 1.6J instead. If a device, or the system behind it, can reach the internet, it can report to PulseGrid.
It is a REST API, not an SDK or a gateway to install. You provision your terminals, point your software at the endpoints, and post heartbeat, transaction, and error events as they happen. Most teams have events landing within an afternoon, and a built-in simulator lets you test before any hardware is on site.
No. A transaction event carries an amount, currency, status, payment type, product, and timestamp — there is no field for a card number, cardholder name, or CVV, and the ingest API rejects them. PulseGrid records that a payment happened, never its contents, and it never moves money.
Devices send heartbeats. If one has not checked in within the window you set for your organisation, it flips to offline and alerting fires. You set the window, because a device reporting every 30 seconds and one reporting every 10 minutes are both perfectly healthy.
Yes. The developer console includes a simulator that sends real heartbeats and payment events through the same API, with a live feed of exactly what arrived — so you can watch the whole flow end to end before a single device is on site.
Yes. Analytics export to CSV on the Starter and Pro plans, and every figure on the dashboard is also available through the same REST API that ingests your events, so nothing is locked in.
Seven days on Free, 90 days on Starter, and one year on Pro. Raising your plan makes older data visible again — queries are clamped to the plan window rather than the data being deleted at the boundary.
The Free plan covers 3 terminals and 1 user at €0, with no card required. Starter is €29/month for 25 terminals, 3 users, 90-day history, and CSV export. Pro is €10 per terminal per month with unlimited terminals and users, 1-year history, and a 99.9% SLA.