API Reference/Session
GET
/v1/auth/me

Authorization

AuthorizationRequiredBearer <token>

In: header

curl -X GET "https://api.descope.com/v1/auth/me" \
  -H "Authorization: Bearer <token>"

OK

{
  "loginIds": [
    "string"
  ],
  "userId": "string",
  "name": "string",
  "email": "string",
  "phone": "string",
  "verifiedEmail": true,
  "verifiedPhone": true,
  "roleNames": [
    "string"
  ],
  "userTenants": [
    {
      "tenantId": "string",
      "roleNames": [
        "string"
      ],
      "tenantName": "string"
    }
  ],
  "status": "string",
  "externalIds": [
    "string"
  ],
  "picture": "string",
  "test": false,
  "customAttributes": {},
  "createdTime": 0,
  "TOTP": false,
  "SAML": false,
  "OAuth": {
    "property1": false,
    "property2": false
  },
  "webauthn": true,
  "password": true,
  "ssoAppIds": [
    "string"
  ],
  "givenName": "string",
  "middleName": "string",
  "familyName": "string",
  "editable": true,
  "SCIM": true
}

Was this helpful?

Refresh Session POST

### Refresh the session token, using a valid fresh token This API endpoint will provide a new valid session token for an existing signed-in user, by validating the provided refresh token. The refresh token is provided as part of the HTTP Authorization Bearer. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <Project ID:Refresh JWT>`

Get Session History GET

### Get user's session history This API Endpoint will return the current user's session history including geo-location and IP address. This endpoint requires the user to be signed in and have a valid `refreshJwt`. The `refreshJwt` is then used as part of the Authorization Bearer to perform this task. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <Project ID:Refresh JWT>`