When the POS is offline

Power cuts and dropped internet happen at dinner time. A quiet POS never closes a store: it stays open on Laayo, the owner is told, and they can take over from the vendor app.

#Heartbeat

Send POST /v1/heartbeat every 60 seconds. store_ids lists the stores this POS is running for; leave it out to mean all your linked stores.

POST /v1/heartbeat

{ "store_ids": [27], "pos_version": "nRestro 4.12" }

200
{
  "data": {
    "server_time": "2026-11-01T12:31:00+05:45",
    "stores": [ { "store_id": 27, "online": true } ],
    "next_heartbeat_seconds": 60
  }
}

#When we stop hearing from you

#Owner takeover

When your POS is down, the owner can switch to Laayo's own controls in the vendor app, for up to an hour. Meanwhile:

• Store, item and order writes from the POS return 409 owner_takeover, so a POS that comes back cannot undo what the owner just did. The message says until when.
• Orders still reach you as events, so your screen stays in step.
• GET /v1/stores/{id}/status shows owner_takeover with active and until, and GET /v1/partner/stores shows owner_takeover_until per store.

409
{ "error": { "code": "owner_takeover",
  "message": "The restaurant is managing this store in the Laayo app until 1:45 pm. Your changes are paused until then." } }

#What your POS should show

• A plain note while takeover is on, for example: Laayo is being managed from the Laayo app until 1:45 pm.
• Keep the cashier's changes queued, and send them after that time.
• If you have been offline, a line saying Laayo orders may be waiting, and fetch them.

#Coming back

• Send a heartbeat first. The store shows online again.
• Catch up on events: webhooks retry for about 24 hours, and polling picks up from your saved cursor. See Retries.
• Read GET /v1/stores/{id}/status before sending a status, in case the owner changed it while you were away.