Changelog
Plans by active connections, and the connection limit error
Plans now differ only in how many active connections a utility serves: Free up to 10, then 100, 250 and 500, with every feature and unlimited team members on all of them. Past 500 there is a custom plan. Pending, suspended, disconnected and retired connections don't count, and the monthly invoice uses the active count on the day it's issued.
No plan charges for connections past its limit. Instead, when the utility is at the limit, the two actions that make a connection active refuse the next one:
POST /connections/{id}/activate(completing an installation);POST /connections/{id}/reconnect(reconnecting a suspended or disconnected connection).
Both answer 409 with error_code subscription.connection_limit_reached and the params max, plan_code and next_plan_code (custom on the 500 plan). Creating applications and approving service requests are unchanged: they leave the connection pending.
What to change in your integration#
If you activate or reconnect connections through the API, handle the new 409: show the message, and point the utility to its subscription settings to change plan. See API errors and the help article on plans and customer limits.
Public endpoints for plans, connectors, and contact requests
The public API now exposes three unauthenticated endpoints for direct use by the public website:
GET $PUBLIC_API/plans: returns published plans ordered bydisplay_order, including limits, pricing, and capabilities.GET $PUBLIC_API/connectors: lists enabled connector drivers (payments, messaging, meters) and their capabilities.POST $PUBLIC_API/contact-requests: accepts contact inquiries with server-side validation and per-IP/email rate limiting.
Standard RateLimit-* headers on rate-limited responses
Where rate limiting applies, API responses now include RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset, plus Retry-After on 429 Too Many Requests responses.
Request-Id on all responses and create idempotency
All API responses now carry the Request-Id header, and application/problem+json error bodies include the matching request_id field alongside a type URL pointing to the error code reference.
Idempotency-Key support (with 24-hour retention and 409 conflict detection when reused with a different payload) has been extended across create endpoints in the business and consumer APIs.
Simulated payment connector and sandbox advance
New accounts created from the sandbox flow (?next=sandbox) now land directly in a pre-seeded sandbox environment with sample customers, connections, meters, readings, network zones, and invoices.
A simulated payment connector is also available exclusively in sandbox tenants, using magic values in the last two cents of the amount (00 confirms, 02 fails, 05 expires, and 09 stays pending until you run sandbox advance in the CLI).
Standard Webhooks headers and whsec_ signing secrets
Webhook deliveries now follow the Standard Webhooks specification. Previous custom headers have been replaced by webhook-id, webhook-timestamp, and webhook-signature, and signing secrets now use the whsec_ prefix. The User-Agent header reflects the configured short brand name.
What to change in your integration#
Update your verification handler to read the new headers and compute the HMAC-SHA256 signature over "{webhook-id}.{webhook-timestamp}.{body}" (or use any off-the-shelf Standard Webhooks library).
Before#
const sig = req.headers['x-signature']
const eventId = req.headers['x-event-id']
const valid = verifyHmac(secret, req.rawBody, sig)
After#
import { Webhook } from 'standardwebhooks'
const wh = new Webhook(process.env.WEBHOOK_SECRET) // whsec_...
const payload = wh.verify(req.rawBody, {
'webhook-id': req.headers['webhook-id'],
'webhook-timestamp': req.headers['webhook-timestamp'],
'webhook-signature': req.headers['webhook-signature'],
})