# Returns details on asynchronous jobs to modify a Group's members

The calls to the POST, PUT or PATCH  endpoints trigger a series of asynchronous jobs to create or update the list of the Group's members.

As these tasks are asynchronous, those API calls do not respond with the final list of the Group's members, but an unique Job identifier to inquire about the task.

This endpoint takes the  identifier, and returns details about the asynchronous job's execution.

The job could have already finished or still be running, and the response could include details on the number of members added, removed, processed, and error conditions (if any).


Endpoint: GET /v2/Groups/JobReport/{jobId}
Version: v2
Security: oauth2_as_a_server, oauth2_as_a_user

## Path parameters:

  - `jobId` (integer, required)
    The unique identifier of one asynchronous Job

## Response 200 fields (application/json):

  - `id` (integer)
    Job unique identifier
    Example: 127

  - `groupId` (integer)
    Group unique identifier
    Example: 3242

  - `status` (string)
    Whether the asynchronous job is still ongoing or it has finished
    Example: "finished"

  - `requestType` (string)
    The type of request that launched the asynchronous job
    Example: "group_update"

  - `requestedChanges` (string)
    JSON string wih details of the number of members to be changed by the API request
    Example: "{\"create\":4,\"destroy\":7}"

  - `requestReceivedAt` (string)
    Date and time when the asynchronous job was launched
    Example: "2024-04-11T12:59:28.043Z"

  - `membersCreatedCount` (integer)
    Number of members added to the group

  - `membersRemovedCount` (integer)
    Number of members removed from the group
    Example: 1

  - `membersProcessedCount` (integer)
    Number of members processed. It could include additions, removals, or users ignored (for example, for being already in the group, or not being members of the program)
    Example: 11

  - `membersPendingCount` (integer)
    Number of members pending to the processed

  - `messages` (string)
    Additional details compiled during the job's execution, if any relevant applies, specially those related to the total number of members processed. For example: number of users not considered, for already being members, or users asked to be both added and removed, or system errors...
    Example: "4 user(s) not added (already members?); 6 user(s) not removed (not members?)"

## Response 400 fields (*/*):

  - `schemas` (array)
    Example: ["urn:ietf:params:scim:api:messages:2.0:Error"]

  - `detail` (string)
    Example: "Reason for bad request"

  - `status` (integer)
    Example: 400

## Response 401 fields (*/*):

  - `schemas` (array)
    Example: ["urn:ietf:params:scim:api:messages:2.0:Error"]

  - `detail` (string)
    Example: "Authentication failure"

  - `status` (integer)
    Example: 401

## Response 403 fields (*/*):

  - `schemas` (array)
    Example: ["urn:ietf:params:scim:api:messages:2.0:Error"]

  - `detail` (string)
    Example: "Operation is not permitted"

  - `status` (integer)
    Example: 403

## Response 404 fields (*/*):

  - `schemas` (array)
    Example: ["urn:ietf:params:scim:api:messages:2.0:Error"]

  - `detail` (string)
    Example: "The requested resource was not found."

  - `status` (integer)
    Example: 404