Electricity Tariff Territories Explained


| Reading time 1 minute

Many utility companies charge different rates based on the geographic location of the customer.  This is particularly true in CA, NY and MA where utilities such as California’s PG&E and Southern California Edison implement territory based pricing.  Up until now, with our APIs it has been a multi step process to get the rates for a tariff for a customer.  However, this week we’ve simplified that so we automatically determine the correct territory if you pass in the customer’s zip code.  I’d like to walk through two scenarios in this post.

Get Tariffs (API)

When you search for tariffs by zip code, you get back a list of all tariffs that are available in that zip code along with various properties on the tariffs.  One of these properties may be ‘territoryId’ which, if present, indicates that this tariff’s rates will vary based on geographic location.  The list of territories served is included as choices of the territoryId property.  What we have now added is a way to indicate which territoryId matches up to the zip code you’ve passed in.

Looking at the example in our docs (link above), you can see the default territory identified as 3538:

 "description":"Territory id where tariff is operational",
<strong> "propertyValue":"3538",</strong>
<strong> "isDefault":true</strong>

Setting the Territory for an Account (API and Genability Explorer)

If you’ve played around with our Storage and Account APIs, you know that you can save various properties on an Account such as the Account’s customer class (Residential or General), zip code and tariff.  What we’ve added now is that when you’ve added a zip code and a tariff to an Account, we automatically check if the tariff is priced based on territories, and if it is we set the corresponding territoryId property on the Account.  This gets updated as needed when the zip code or the tariff id on the Account get updated.

When you’re setting up an Account in Genability Explorer, this same behavior occurs.  Set the Account’s zip code and tariff and we will set the territoryId accordingly, when applicable.

I hope that simplifies your life a bit.  As always, let us know if we can help you out with any project you are working on by sending a mail to

Also in Products

Genability Explorer Supports Demand Values

By John Tucker | Jan 10, 2012

We’ve been very busy over the past few weeks, and not just with the holidays.  We’ve been busy processing the deluge of new year rate updates including Pacific Gas & Electric, Southern California Edison, San Diego Gas...

Matching your Utility Bill in our Explorer Web Application

By John Tucker | Nov 30, 2011

The first thing most of our customers do when logging into Genability Explorer for the first time is try to reproduce a utility bill. They take either their bill from home or one their customer’s bills and...

Electricity Tariff Glossary

By John Tucker | Nov 17, 2011

Since we launched Genability at the end of last year, we’ve been often asked for a quick start to understanding electricity tariffs.  With that in mind,we put together a simple glossary of electricity tariff features, complete with...

Real time vs Caching Data in Genability APIs

By Emile Baizel | Sep 7, 2011

One question we hear a lot is whether our pricing data is intended to be cached or served up real time.  The short answer is that we design our APIs to be accessed real time.  One of...