Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nomos.energy/llms.txt

Use this file to discover all available pages before exploring further.

If you’re running a white-labeled energy product on Nomos, your customers should never see our brand. The same API that powers our hosted portal is available to you: the contract, the invoices, the meter readings, the historical consumption.

What you’ll wire up

1

Read the active subscription

Retrieve a subscription returns plan, status, address, start and end dates, and projected annual usage. Enough to render a “your contract” card.
2

List invoices

List invoices under the subscription, with filters (status, period_start) and pagination. Link directly to the hosted PDF rather than re-rendering the document.
3

Submit a meter reading

For analog-meter customers, Create a meter reading accepts a value in kWh and a timestamp. If the value is implausible, the API rejects it with UNPROCESSABLE_ENTITY; show that as a soft hint, not a hard error.
4

Show consumption

Retrieve consumption data returns 15-minute intervals (smart meters) or monthly totals (analog). Pair it with Retrieve a price time series to show “you used X kWh during cheap hours.”
5

Keep state fresh

Subscribe to webhooks; your portal stays in sync without a single cron job.

State you’ll listen for

WebhookWhat changes in the portal
subscription.activatedUnlock the live-contract view, prices, consumption.
subscription.terminatedShow the offboarding state and end date.
subscription.endedArchive the user.

FAQ

Run your own identity. Map your user record to the Nomos customer.id (or subscription.id) and use server-side Client Credentials when calling Nomos.
Yes. Each invoice has a hosted URL on the response. Link to it; don’t proxy or re-render the document.
The API runs plausibility checks against recent values and rejects with UNPROCESSABLE_ENTITY when something looks off. Surface the rejection as “this number looks off, double-check” rather than a fatal error.
No. Drive portal state from webhooks. The same events that change the subscription’s status trigger your portal’s render path.