Connect the hardware you have.
A practical guide to sending clean, traceable device data into your ERP with nestastack. API examples are illustrative; demo keys do not access a live service.
Start here
Create a workspace, choose a plan, and complete checkout to unlock your workspace API key.
A predictable path from device to ERP.
nestastack accepts events from device APIs, gateways, vendor clouds, and webhooks. Normalize once, validate the payload, then route it to the correct ERP record.
Authenticate each request
Send your workspace key as a bearer token over HTTPS. Create a key from the console after checkout. In this preview, checkout is simulated and the generated key is demo-only.
curl https://api.nestastack.example/v1/events \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d @event.json{
"event_id": "evt_01HZX8K3",
"event_type": "attendance.punch",
"occurred_at": "2026-11-04T08:42:16Z",
"source": { "device_id": "clock_014" },
"employee": { "external_id": "EMP-2048" },
"direction": "clock_in"
}Integration patterns
Use the same event endpoint for each source. Map vendor-specific fields to the common payload before routing.
Attendance hardware
Send clock-in and clock-out events with a stable employee identifier and the source device ID.
event_type: attendance.punchGPS & fleet
Send timestamped coordinates and vehicle identifiers. Add geofence or trip metadata when available.
event_type: fleet.locationMeters & sensors
Send numeric readings with a unit, asset identifier, and optional threshold state.
event_type: sensor.readingERP to ERP
Use a source and destination system pair to move validated records between ERP environments.
event_type: erp.recordHandle retries safely
Use a unique event ID for idempotency. Retry rate limits and temporary server errors with exponential backoff; send invalid payloads to a review queue.
Sign in, choose a plan, then create your demo key from the console.