Copy EX 360 Subjects

POST {{baseUrl}}/ex-projects/:projectId/copy-subjects

Copy subjects identified by given list of uniqueIdentifier from employee directory to project. Subject's metadata in employee directory is also copied into project.

Starting More Than Ten Concurrent Jobs Results in HTTP 409 Error

This API starts an asychronous job for a project on our servers. If you try to create more than ten jobs of any kind for any project, the eleventh job will return a 409 error. Please catch that error and handle it appropriately (do not continue to try to start new jobs).

Processing Order of Jobs

The processing order for jobs is first in, first out for each job context (where the job was started). Jobs in different projects can run concurrently, but only one job from each context can run at one time. Global Directory jobs will not start until all jobs started in a different context are complete. Also, no other jobs can run concurrently with Global Directory jobs. Jobs started while Global Directory jobs are processing must wait until the Global Directory jobs finish before they can begin to process.

Here is an example queue showing order of job processing based on the jobs' contexts and projects.
| Jobs | Process | |-------------------------|-----------------------------------------------------------------------------------------------------| | Job 1: Project A | | | Job 2: Project B | Job 1 and Job 2 can run simultaneously, because they are in different projects. | | Job 3: Global Directory | Job 1 and Job 2 must finish before Job 3 can run, because Job 3 is a Global Directory job. | | Job 4: Global Directory | Job 3 must finish before Job 4 can run, because they're in the same job context (Global Directory). | | Job 5: Project A | Job 4 must finish before Job 5 can run—it has a different context than Global Directory. | | Job 6: Project A | Job 5 must finish before Job 6 can run because they share a project. |

Request Body

{"uniqueIdentifiers"=>["<string>", "<string>"]}

HEADERS

KeyDatatypeRequiredDescription
Content-Typestring
Acceptstring

RESPONSES

status: Created

{&quot;jobId&quot;:&quot;\u003cstring\u003e&quot;,&quot;meta&quot;:{&quot;httpStatus&quot;:&quot;\u003cstring\u003e&quot;,&quot;requestId&quot;:&quot;\u003cstring\u003e&quot;,&quot;notice&quot;:&quot;\u003cstring\u003e&quot;}}