PiBox » Iron Man

h1. REST APIs

h2. Server Node (imwww)

table{width:100%}.

|_. Resource Name |_. HTTP Verbs  |_. HTTP Methods            |_. Returns    |_. Direction   |_. Description |

| Pair            | CREATE Pair   |  POST /pair/              | UUID         | From IoT Node | Pair an IoT node w/ server |

| Pair            | CREATE Pair   |  POST /pair/register      | ACK          | From IoT Node | Register an IoT node w/server using UUID |

| Pair            | CREATE Pair   |  POST /pair/jarvis/<uuid> | Public keys  | From Jarvis   | Pair a Jarvis node with server |

| 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 |

Notes

* Monitor identity includes location and possibly other descriptors that uniquely identify the monitor

h2. IoT Node (embedded in Arduino device code)

table{width:100%}.

|_. Resource Name |_. HTTP Verbs |_. HTTP Methods      |_. Returns    |_. Direction |_. Description |

| Device          | UPDATE Device|  PUT /device/<uuid> | Device state | From Server | Change device state with JSON |

| Device          | GET Device   |  GET /device/<uuid> | Device state | From Server | Get Device state as JSON |