Dashboard will let you know if there have been failures billing your credit card
More alerting if your balance goes negative and we now default to trying to bring your balance back up to zero instead of pausing SIMs if balance goes negative
More instructions on the Dashboard for setting APN for newer users
Fixes to how overage was billed after a plan change (was chance of overbilling if you went from monthly to Pay-As-You-Go that’s now resolved)
Lots of internal architecture changes to parts of our carrier integrations. May have been some temporary SMS issues while that was rolling out but should be fixed now
Had to put some extra restrictions on organization invites to prevent system being abused. If you run into an issue preventing your deployment from working, please email us.
Catch carrier error conditions in our system better to prevent things like missing SMS messages when carrier has an outage and try to be faster at resolving issues like a SIM stuck in the activation state
Fix issue where an account refill might trigger twice on a new account when auto refill is enabled while activating
Fix some typos on Dashboard
Better communication of service alerts on Dashboard
Made device tagging API endpoints a little easier to use by not requiring orgid to be sent if the devices are on a custom org. (Though the devices should match the org of the tag. See docs for more info)
Device tagging should also be much faster now when tagging a large number of devices
Get bulk tower location data by setting withlocation=true on the /devices API call. (Previously location data would only work when looking at a single device.) See API docs for more information.
Device objects on /devices now show latest IMEI value for device. We will show the IMEI and the IMEISV. Previously only IMEISV was shown on lastsession object. IMEI was added as this is usually what will match the label on the physical device.
Can now search devices by imei with ?imei=<imei> and ?imei-sv=<imeisv> URL parameters
New SIM inventory feature. (More information on this coming soon.)
Fix issue that sometimes prevented people from updating email address.
Fix some bugs people were seeing with activation and give better error messages for some failure cases.
Connection details on the device page will now show the technology being used by the connection (2G, 3G, or LTE) if the carrier is able to report that data to us
Routes let you flip between an OR and AND comparison for the topics you select. This will let you build routes that only match if all of the topics on the route are on the message. Previously, all routes were OR which meant they would fire if any of the topics on the route were on the message.
We have deployed more sophisticated rate limiting to maintain quality of service on the API. Most people probably won’t ever run into it, but if you are making too many requests you’ll receive a 429 response. See docs for more information.
Basic SMS delivery receipts: if the network indicates that an SMS you sent to a device was delivered, you’ll now see a message with the topic _SMS_DT_DELIVERED_ to indicate that. It doesn’t track to a specific message yet, just that a message you sent was delivered to the device.
Organizations with large numbers of devices should see better API performance when filtering /devices via IMSI
/devices endpoint now has a states filter to show devices with a specific state set
IMEI changes now trigger messages in the data engine. The first time we see an IMEI for a SIM, you’ll get a message with _IMEI_FIRST_. If an IMEI changes, you’ll get _IMEI_CHANGE_ which can also have the topic _IMEI_TAC_CHANGE_ if the first 8 digits of the IMEI changed which indicates a totally different hardware type. (Note that this message will trigger within a few minutes of session close.)