Advanced webhooks now supports more complicated variables where it will parse json objects and allow you to access things by doing <<decdata.fieldname>>
Fix some bugs with the heartbeat app and add better styling to the configuration page for it
New feature to allow sending data messages down to any device via a text box on the dashboard, our API, or a preauthenticated webhook. Supports TCP and UDP on any port and responses will show up in your data logs. (Docs coming very soon for this) The current version of the Dash firmware doesn’t support this, but that is coming soon, too. For now, you can test with a USB modem and Raspberry Pi, or some similar setup.
Losant and IFTTT integrations are available for our cloud. (We’ll post some docs about these next week, but it should be fairly straightforward to use right away)
/csr/sources API call now reports ASCII versions of the keys
Fix issue where routes on an organization couldn’t be enabled or disabled
Fix issues with autocomplete on topics
Some layout and design tweaks on the dashboard
Fix issue where our cloud would sometimes fail to verify a server SSL certificate and cause a webhook route to fail
Add support for bulk operations on dashboard. Send SMS or pause and resume or perform other operations on multiple devices at the same time. (Keep an eye out for more information about this feature.)
Several bug fixes and performance improvements in the API.
Add ability for users to transfer devices between organizations. Must be owner of the source organization and be owner or have activation privileges on receiving organization. Can do the transfer via the dashboard by clicking on the Manage menu at the top of the device list or via API by setting orgid on PUT /devices/.
Fix bug with organization invites sometimes sending an incorrect URL
Add new “Matched Routes” column on Data Logs to show which routes were hit by that particular message and if there were any failures.
Laying some groundwork for other improvements to the cloud
For those using generated cloud credentials to send messages to our cloud, the ID and key have been combined into a single 8-byte key. Sending as separate fields will still work for now so nothing should break. We’ll be pushing an update to our docs in the next day or so with more information on this.
Lots of bug fixes and optimizations across the platform
Over the last couple weeks we’ve been doing some deployments. Biggest change was the new routes and logging features, but there have also been some performance improvements and little bug fixes that we hope you all enjoy.
Users must now verify their email address before activating a SIM card
Fixed some issues that were making verification difficult for some people
New routes view on individual devices in dashboard
Other small bug fixes
Edit: Forgot one:
Changed output of /plans API endpoint. Zones are now listed in an array instead of having the separate amountX, smsX fields. Those fields are still there but will be removed at some point in the future.
Advanced Webhook Integration now allows you to specify any HTTP headers you want. You can use variables in the header values to pass data along from your device
Dashboard should give you the option to resend verification email if you can’t activate due to verification failure
For smaller orders, SIM cards will now show up in your account automatically once they’re shipped to you so you don’t have to type in the number to activate.
You can now set a name for your SIM on activation instead of having to rename later
Fix some issues on IE11
Route device and tag topics will now show the name instead of the ID
Built-in support for HTTP authentication in webhooks
Activation API endpoint now accepts zone as an alias for tier and you can specify a tagid to tag all the devices you just activated. (This will be integrated into dashboard soon)