Build API goes into open beta phase

IDE & Tools
1

More info here, plus info on getting your API key via the IDE.

Updated Build docs here.

2

Great job guys ! I like the fact you don’t need to request API keys through support (although they’re more than helpfull, I guess you have better things to do then generating keys :slight_smile:

First observation:

device restart (eg. build.electricimp.com/v4/devices/23509b4cead3dbee/restart) seems to give systematic “ResourceNotFound” code.

{
“success”: false,
“error”: {
“code”: “ResourceNotFound”,
“message_short”: “Unknown route GET /v4/devices/23509b4cead3dbee/restart”,
“message_full”: “Unknown route GET /v4/devices/23509b4cead3dbee/restart”
}
}

GET device (eg. build.electricimp.com/v4/devices/23509b4cead3dbee) for the same device works perfectly fine…
Tested with 3 devices with same result

3

Solved…by using POST iso GET (as clearly indicated in the docs …stupid me :-))

4

For anyone interested - I released an NPM package for the Build API. It wraps most of the core functionality, and is a great starting point if you’re building Javascript based tools :slight_smile:

5

This is great, have you thought about implementing web hooks for things like device online status?

6

Also any chance or CORS support and maybe finer grained permissions on the keys e.g. ability to create a read-only key for the /devices/{id}/logs endpoint.

7

Neither of these are part of the current spec, @jdelaune, but I’ll add them to our list of user-requested features.