OPS: deboardgemgroup

OPS: Deboard GEM Group

This call should be made in order to remove an entire Gem group from whatever state they may be in and put them back into a one of two states, based on the "requeue" parameter. If requeue is true, they will be placed back into the onboarding queue. They will be grouped by their original subgroups and the deboard GEM Group will cease to be valid.

Endpoint: /api/v1/ops/deboard/gemgroup

Verb: POST

Payload:

The request payload contains several optional fields that allow you to choose how you wish to reference the user to be deboarded. One of them must be provided. If more than one is provided, only one will be used to select the user, and the others will be ignored.

Type	Attribute	Required	Description
Bool	requeue	Yes	Specifies whether the members of the group should be placed back in the onboard area queue. If this value is false, they will be placed into the general pool of usrs that have valid tickets but have not been scanned to enter the onboard area yet.
uint64	group_id	No	Specifies the ID of the GemGroup record that is being deboarded
string	user_scan_id	No	Specifies the Scan ID of any member of the GemGroup that is being deboarded
string	device_scan_id	No	Specifies the Scan ID of the Device assigned to any member of the GemGroup that is being deboarded

Example Response:

{
    "api_code": 0,
}

or

{
    "api_code": xxxx,
    "error": {
        "error_code": xxxxx,
        "error_message": "Erorr message",
        "error_detail": "Optional additional details about error",
        "suggestion": "Optional suggestion on how to resolve error",
        "callstack": "Optional debug callstack."
    }
}

See https://studio.wevr.com/wevr/projects/gem/gem-platform/-/wikis/GEM-API-Codes for error codes contained therein.

See https://studio.wevr.com/wevr/projects/gem/gem-platform/-/wikis/GEM-Server-Codes for error codes contained therein.