Session User
Returns the userId of the calling user.
Header parameters
sessionTokenstringRequired
Session authentication token.
Responses
200
OK
application/json
400
Client error, see response body for further details.
application/json
401
Unauthorized: Invalid session token.
application/json
403
Forbidden: Caller lacks necessary entitlement.
application/json
500
Server error, see response body for further details.
application/json
get
/v2/sessioninfoGET /pod/v2/sessioninfo HTTP/1.1
Host: yourpodURL.symphony.com
sessionToken: text
Accept: */*
{
  "id": 7696581394433,
  "emailAddress": "[email protected]",
  "firstName": "Symphony",
  "lastName": "Admin",
  "displayName": "Symphony Admin",
  "title": "Administrator",
  "company": "Acme",
  "username": "[email protected]",
  "location": "California",
  "accountType": "NORMAL",
  "avatars": [
    {
      "size": "original",
      "url": "../avatars/izcQTdRVFOK_qhCrYeQOpIuHKuZuMk3J88Uz_bShzM8.png"
    },
    {
      "size": "small",
      "url": "../avatars/izcQTdRVFOK_qhCrYeQOpIuHKuZuMk3J88Uz_bShzM8_small.png"
    }
  ],
  "workPhoneNumber": "+33901020304",
  "mobilePhoneNumber": "+33601020304",
  "jobFunction": "Sales",
  "department": "APIs",
  "division": "Partnerships",
  "roles": [
    "INDIVIDUAL",
    "SUPER_ADMINISTRATOR"
  ]
}When calling this as an OBO-enabled endpoint:
Use the OBO User Authenticate token for
sessionToken.An OBO application must include the Primary User Identity (GET_BASIC_USER_INFO) permission, along with all other required authentication and permissions. See App Authenticate and OBO-Enabled Endpoints.
See Bot Permissions for a list of roles and associated privileges.
Last updated
Was this helpful?