Knowledge base ·
How to get a SolaX Cloud API token
A token is how you give a service read access to your system's data without giving it your account password. With SolaX you generate one yourself in the portal, it's free, and it takes a minute.
This guide covers where to get it, what it can and can't do, and what limits it carries — including the inconvenient ones you're better off knowing in advance.
What you'll need
Two values. They get mixed up surprisingly often, so here's the difference up front:
| Value | What it is | Where it lives |
|---|---|---|
| Token (tokenId) | A long number that only reads data | Generated in SolaX Cloud |
| Registration number | The number of the communication module (Wi-Fi/LAN "dongle") | On the module's label and in the device list |
The registration number is NOT the inverter's serial number. It's the number of the small box plugged into the inverter that handles the internet connection. Entering the inverter serial is by far the most common reason a connection fails.
The steps
- Sign in to SolaX Cloud — web or mobile app, the same credentials you use to watch your production.
- Open Service → API and generate a token (
tokenId). - Find the registration number of the communication module — it's on its label and also in the device list in your account.
If the section isn't where this describes, don't panic: SolaX Cloud runs on
several regional instances (global.solaxcloud.com, www.solaxcloud.com
and others) and the interface differs between them and between versions. Look
for an item named "API" or "Token" under account or service settings.
What the token can and can't do
This is the part most guides skip, and it determines what to expect from connecting.
It can: read the current state of the system — instantaneous power, today's and lifetime production, the power of individual panel strings, battery state, flows to and from the grid, and the inverter's status code.
It can't: pull history. SolaX's user API returns none — verified in the documentation of both versions (User Monitoring API V6.1 and User API V2.0). That has a direct consequence for any service working through the token: production over a period has to be computed from the difference between two readings, which means the value starts on the day you connect and grows with time. Anyone promising the token will instantly show you last year is either getting it elsewhere or isn't telling the truth.
One exception: the inverter keeps cumulative counters since installation (total production, total exported, total imported). Those support a rough lifetime balance from the very first reading — but it's an average over the whole operating life, not month-by-month history, and it has to be treated as such (see a lifetime production estimate from a single reading).
Limits: 10 requests per minute and 10,000 per day per token. For monitoring a system that's ample; it simply means reading periodically rather than continuously.
Security — what to watch
- The token is a credential. Treat it like a password: don't send it in an unencrypted message and don't publish it in a screenshot.
- It grants read access only. This route cannot control the inverter or change settings — that's a property of the API, not a promise.
- Access ends where it started. Your SolaX Cloud account issued the token, and managing it stays there.
- Never hand anyone your account password instead of a token. The difference between the two is exactly what they allow.
How it works with us
When you enter the token and registration number on the connect SolaX page, this happens:
- The values are encrypted and stored; the token is never returned to the browser and never travels in a page address.
- A first reading runs, and you immediately see the current state of the system.
- After that we read automatically several times a day. You don't have to do anything else.
- You get a link to a report. Save it — that's your way back to the result.
What accrues over time, because history has to be measured:
| When | What it gives |
|---|---|
| Immediately | Instantaneous power, battery state, string power, grid flows |
| After a few sunny days | Strings compared against each other — a shaded or disconnected string |
| After the first full month | Monthly production against expectation for your location |
| After three months | How much output stays at home and how much goes to the grid |
| After a year | An annual assessment at the highest confidence |
What we can tell from the very first reading, regardless of history: a fault the inverter reports about itself, and a disconnected or failed battery. Those findings infer nothing from production data, so they need no accumulated series — see inverter status codes.
If the connection fails
The three most common causes, in order:
- The inverter serial number entered instead of the module's registration number. See above — it's by far the most frequent.
- A token from a different regional instance. An account on
www.solaxcloud.comand one onglobal.solaxcloud.comare not the same. - A typo. The token is long; copy it, don't retype it.
Don't have a SolaX?
So far it's the only brand we can read. The others differ substantially — some offer a token just as freely, others lock the API behind an installer account or a contract. We wrote the differences up in which inverter brands let you access your own data.
In the meantime the quick check works without any connection — it only needs a few figures copied from the app you already have.
Want to know how yours is doing?
The quick check compares your output against what your location should deliver. Minutes, no sign-up.
Run the check →