Bootstrap the authenticated mobile workspace
const url = 'https://api.vocapable.com/v1/mobile/me';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
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://api.vocapable.com/v1/mobile/me \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Successful Response
The authenticated app’s identity/bootstrap response at GET /v1/mobile/me.
Operational selector data (contacts, agents, schedules, team rows) deliberately stays on its own capability-gated endpoints. This profile contains only the facts every app boot needs and no push token or refresh/session secret.
object
object
The only roles a customer can hold in one workspace.
What this person may do in the company, as the workspace decides it (CC7-R2).
capabilities (on :class:MobileBootstrapProfile) says which native surfaces exist
for the session; these are the workspace capabilities behind them - the built-in role’s
set, or the custom role’s after the same narrowing every request applies - and the
person’s team scope. The app gates screens, tiles and buttons on them instead of on the
role name (a custom role sits on a manager membership whatever it grants). The
server still decides every request; this only says what not to offer.
object
Example
{ "membership": { "role": "admin", "status": "active" }, "capabilities": [ "activity:read" ], "device": { "platform": "ios", "status": "active" }, "permissions": { "workspace_capabilities": [ "view_all_customers" ] }}