Lock or unlock
Changed onStart a new lock session or complete (unlock) the active session. User IDs (target and keyholders) are validated against your accessible users before the action is performed. When starting a partner's lock, the authenticated user is automatically assigned as a keyholder, including when keyholderIds is omitted or empty. OAuth partner starts require lkbx:keyholders. A definitive Chaster creation rejection cancels the local session before returning an error. If Chaster's outcome is uncertain, the response is 201 with the created lockSessionId and a warning; inspect the current session and do not retry creation blindly.
Request
- Base URLhttps://dashboard.researchanddesire.com/api/v1
- Auth
- HTTP bearer
- or OAuth 2Authorization code/oauth/authorizeToken URL/oauth/tokenScopeslkbx:control
Request body
Response
Lock session completed
Changes
- info
added the optional property
/to the response with the status
- info
- info
the endpoint scheme security
bearerAuthwas added to the API - info
the endpoint scheme security
oauth2was added to the API
- info