Overview
The /1/authorize endpoint allows for the removal of authorizations made via /1/authorize - POST
...
When a learner is created via /1/learner - POST, it can only be assessed by the user that was provided when the learner was created. If multiple users (created by /1/user - POST) need to perform assessments on a single learner, /1/authorize - POST can be used to authorize subsequent users to perform assessments on the learner.
...
Info |
---|
|
User-Agent | <company identifier> | The exact value here is not important, but it should include something to identify your company | Authorization | Bearer <your token> | Bearer wV1MLk5+sFzioJw/3M5r9A== | Content-Type | application/json |
| X-LearnerId | <the learner id> | The DMTD-supplied identifier that identifies the learner (see Getting startedREST API Guide and /1/learner - POST)* | X-LearnerCode | <the learner code> | A REST-client-supplied identifier that identifies the learner (see Getting startedREST API Guide and /1/learner - POST)* |
*Only one of X-LearnerId or X-LearnerCode is required. If both are specified, X-LearnerId is used.
|
Info |
---|
title | Request Query Fields |
---|
|
Only one of userId or userCode is required. If both are specified, userId is used.
|
Info |
---|
|
HTTP Status | Description |
---|
200 - OK | The call succeeded and the user no longer has permission to assess the given learner. | 202 - Accepted | The given user did not have permission to assess the given learner. | 400 - Bad Request | The body of the request was invalid | 401 - Unauthorized | The caller identified by the Bearer token does not have permission to perform this operation |
|
...