Get My Profile
The signed-in user's profile and display preferences (RO-291). Signed-in users only: an API key gets 403.
API key access
/api/v1/me/profileAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Response Body
curl -X GET "http://localhost:8000/api/v1/me/profile"{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"email": "string",
"name": "string",
"timezone": "string",
"locale": "string",
"theme": "system",
"appearance": {
"surface": "solid",
"glass_blur": 4,
"glass_opacity": 30,
"glass_tint": "warm",
"wallpaper": "ember",
"motion": "full",
"density": "comfortable"
},
"pinned_pages": [
"string"
],
"has_password": true,
"created_at": "2019-08-24T14:15:22Z"
}Export My Data
Download everything ReachOut keeps about you as an account (RO-295): profile, workspace memberships, sign-in sessions, API keys you created, apps you connected, invitations you sent or accepted and your personal notifications. No passwords, tokens, keys or their hashes. Signed-in users only: an API key gets 403.
Me
The current user and every workspace they belong to, with their role in each.