Actions
REST APIs » History » Revision 9
« Previous |
Revision 9/16
(diff)
| Next »
Hammel, 12 Jul 2018 10:00
REST APIs¶
Monitor Node (imwww)¶
Resource Name | HTTP Verbs | HTTP Methods | Returns | Direction | Description |
---|---|---|---|---|---|
Pair | CREATE Pair | POST /pair/iot | UUID | From IoT Node | Pair an IoT node w/ Monitor |
Pair | CREATE Pair | POST /pair/iot/register | ACK | From IoT Node | Register an IoT node w/Monitor using UUID |
Pair | CREATE Pair | POST /pair/jarvis/<uuid> | Public keys | From Jarvis | Pair a Jarvis node with Monitor |
Monitor | GET Monitor ID | GET /monitor | Monitor ID | From Jarvis | Monitor Identify information |
Device | GET Devices | GET /device | Device list | From Jarvis | Get list of device IDs and descriptors |
Device | UPDATE Device | PUT /device/<uuid> | Device state | From Jarvis | Change device state with JSON |
Device | GET Device | GET /device/<uuid> | Device state | From Jarvis | Get Device state as JSON |
- Monitor identity includes location and possibly other descriptors that uniquely identify the monitor
IoT Node (embedded in Arduino device code)¶
Resource Name | HTTP Verbs | HTTP Methods | Returns | Direction | Description |
---|---|---|---|---|---|
Device | UPDATE Device | PUT /device/<uuid> | Device state | From Monitor | Change device state with JSON |
Device | GET Device | GET /device/<uuid> | Device state | From Monitor | Get Device state as JSON |
Device | GET Register | GET /register/<uuid> | ACK | From Monitor | Provides UUID from monitor |
Updated by Hammel over 6 years ago · 9 revisions