Folio. schoolbooks, in one place

Rubrica · the keys desk

Your keys, where they hide.

Token-hungry platforms want a key from your already-logged-in browser. Here’s exactly where each one keeps it. A token is like a password — copy it once, keep it private, and only ever paste it into tools you trust. Folio seals yours into an plaintext Cabinet on your own device.

A —

Browsers & DevTools

Open DevTools

On Windows/Linux: F12 or Ctrl+Shift+I. On macOS: Cmd+Option+I. Right-click → “Inspect” works too.

Enable network log

In the Network tab, tick Preserve log. Hard-refresh the reader page (Ctrl/Cmd+Shift+R) so the book’s API calls appear as they load.

Privacy first
A token grants access to your books. Folio keeps it sealed on your device and uses it only to fetch your own pages. On shared machines, lock the Cabinet or close the tab when you’re done.

Local Storage / Session Storage — find under Application → Storage → Local Storage → https://platform. Look for keys like token, jwtToken, auth_token, tokenId.

CookiesApplication → Storage → Cookies → https://platform. Sometimes the value hides here (bSmart’s _bsw_session_v1_production).

Response headers — in the Network tab, open an API call and read the Response JSON or the Headers. Many platforms return their token in the login response body.

B —

Per platform

HUB Scuola / Young / Kids — token or email & password

Easiest: don’t hunt for a token at all — the Reader logs in with email & password directly. If you prefer a token: log in at hubscuola.it, open the reader, DevTools → Network → ms-api.hubscuola.it call → Request Headers → Token-Session. It’s usually valid a long time.

MyLim (Loescher) — JWT

Log in at mylim.loescher.it. DevTools → Application → Local Storage → https://mylim.loescher.it → the key token (a JWT, starts eyJ…). Paste it in the Reader.

bSmart — session cookie

Log in at my.bsmart.it. DevTools → Application → Cookies → https://my.bsmart.it → copy _bsw_session_v1_production. Paste it in the Reader.

DiBooK (Laterza) — JWT

Open a book in the reader at dibooklaterza.it. DevTools → Application → Local Storage → copy jwtToken. Paste it in the Reader, then add the volume by ISBN.

Everything else — email & password suffices

Zanichelli, Pearson, Sanoma, Educadhoc, WSET and the remaining shelf log in with ordinary credentials — no token hunting needed. Those connectors are next on the docket; the Reader already speaks the same fetch-unlock-merge language they use.

Handle with care. A token is a live credential. What follows in Folio runs where you are: your keys are sealed on your device with a passphrase you choose, and the only network traffic is to the platform you’re already logged into. Anyone asking you to upload a token to a server is a scam — a real downloader always runs where you are.