Hey

tl;dr: We're doing a handful of Area ID changes over the next week or so. So keep an eye on your error logs.

Sometimes, we know in if a Suburb will change (or has changed) from one loadshedding block to another. The ESP App caters for this, and automagically updates the Suburb to the new Area ID so the user doesn't need to do anything.

Take, for example, JHB City Power's recent bunch of adjustments on 17th March 2024. Bruma went from Block 7 -> 13, transforming from jhbcitypower3-7-bruma to jhbcitypower3-13-bruma

What this means for you: After the switch, the old Area ID will start returning HTTP 404 (Area does not exist)

To help out a bit; keep an eye on your logs. If we know the new Area ID we will send it back in the log:

{
    "error": "Error 404: Area does not exist; replaced_by_id=jhbcitypower3-13-bruma"
}

One last thing

Big shoutout to the creators out there using our API! We're on the brink of reaching 10k free API users! 🎉 Huge thanks to the fantastic folks who've gone the extra mile and joined the Professional & Business tiers – your support means the world to us – and it also means we can spend some extra time on making the API even more useful.

Thanks for your support🚀

Jeff

1 comment

Write a comment

EskomSePush API with Outages

ESP API Outage 11/07/2024

ESP API outage

See all posts from ESP EskomSePush