Get a token and make the first request
Where to create an API token in the cabinet, how to pass it in the Authorization header and verify it with /user/info.
Contents: 9
- 1. Open «Account» and find the «Authentication Tokens» section.
- 2. Click «Add» and enter a «Token name», for example the name of your integration.
- 3. Copy the token and store it in the ADV_T environment variable in your terminal.
- 4. Send GET /user/info to api.advision.digital with a Bearer Authorization header.
- 5. Request GET /dashboard to see the cabinet summary: screens, playlists, storage.
- Connection parameters
- Examples
- Account endpoints
- If it did not work
Open «Account» and find the «Authentication Tokens» section.
You will see the list of existing tokens or an empty section with the «Add» button.
Click «Add» and enter a «Token name», for example the name of your integration.
A new 128-character token appears in the list.
Copy the token and store it in the ADV_T environment variable in your terminal.
Send GET /user/info to api.advision.digital with a Bearer Authorization header.
A 200 response with login, role and cabinet fields means the token works.
Request GET /dashboard to see the cabinet summary: screens, playlists, storage.
Connection parameters
Parameter | Value |
|---|---|
Base URL |
|
Header |
|
Format | JSON responses; POST bodies are JSON too, except |
Rights | One token = ownerRole with full access to the cabinet, including members and tokens. level for the whole cabinet |
Sessions | None: to "log out", simply stop sending the token |
Documentation | No Swagger or OpenAPI; paths look like |
Examples
Token check with curl: curl -s -H "Authorization: Bearer $ADV_T" http://api.advision.digital/user/info
The same in Python: import httpx, os; c = httpx.Client(base_url="http://api.advision.digital", headers={"Authorization": f"Bearer {os.environ['ADV_T']}"}, timeout=60); print(c.get("/user/info").json()["cabinet"])
The /user/info response contains the token itself and the e-mail in plain text: do not print it in full to logs or chat.
Account endpoints
Method and path | What it does | Important |
|---|---|---|
| Profile of the current token: | HTTP 200 = the token works; the response contains the plain token |
| Cabinet summary: | Quick health check of the whole fleet in one request |
| Cabinet users ( | Creating users and roles via API is not available |
| Body | Not verified on a live cabinet |
If it did not work
Response | What to do |
|---|---|
401 | The header did not arrive or the token is incomplete: check that you send all 128 characters and the word |
403 | The token was revoked or the object is unavailable: |
500 | Transient API failure: retry 4–6 times with a 2–3 second pause; if the error persists, check the request body |
Related articles
- How-to · 2 minCreate an API tokenAn integration token is created in the «Authentication Tokens» block on the «Security» page and gives full access to the cabinet.
- ReferenceScreens: reading, schedule, statusesEndpoints of the point controller: screen list and card, daily schedule, content assignment, screen capture, device control, networks.
- ConceptTypical scenarios and pitfallsThe four-step rule (read, back up, write, re-read), patch request pitfalls and ready request sequences for typical tasks.