Who am I — the signed-in user
const url = 'https://beta-api.plune.ai/v1/me';const options = {method: 'GET', headers: {cookie: 'plune_session=<plune_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/me \ --cookie plune_session=<plune_session>The current session user (id, email, role, display name, language, theme). The dashboard reads it to show the account and, when you sign in, to open in the language and the theme you chose in another browser.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”The signed-in user
object
The display name (B8-team T3) — what every screen shows where a row names this person, in place of the address. null until given on the Account page.
The language the person chose for the dashboard (#1016), kept with the account so another browser opens in it. null until they choose one: the browser’s own preference stands in, and nothing is written on its behalf.
The theme the person chose for the dashboard (#1016), kept with the account like locale. null until they choose one.
What this account is allowed to be, e.g. user or owner. Open-ended: new roles appear without a client release.
Example
{ "userId": "u-shop", "role": "user", "name": "Olena Kovalenko", "locale": "uk", "theme": "light"}No / invalid session
Session valid but the user no longer exists
object
Example generated
{ "error": "example"}