Reviewing Registration Requests

This section describes how to review and manually approve or decline registration requests. This process applies to registration requests that meet the criteria for manual approval specified by a standard rule for the group or by a pre-auth rule.

To view all registration requests, use the GET method of the mgm/{holdingidentityshorthash}/approval/registrations endpoint.

curl --insecure -u <username>:<password> <REST-API-URL>/mgm/<MGM-HOLDING-ID>/approval/registrations

This method returns the rules in the following format:

  {
    "memberInfoSubmitted": {
      "data": 
    },
    "reason": "string",
    "registrationId": "string",
    "registrationSent": "2022-06-24T10:15:30Z",
    "registrationStatus": "SENT_TO_MGM",
    "registrationUpdated": "2022-06-24T10:15:30Z"
  }

Requests that are pending manual approval have the status PENDING_MANUAL_APPROVAL.

To view requests from a specific member (for example, C=GB, L=London, O=Alice) and include historic requests:

curl --insecure -u <username>:<password> <REST-API-URL>/mgm/<MGM-HOLDING-ID>/approval/registrations?requestsubjectx500name=C%3DGB%2C%20L%3DLondon%2C%20O%3DAlice&viewhistoric=true'

To approve a rquest, pass the ID of the request to the POST method of the mgm/{holdingidentityshorthash}/approve/{requestid} endpoint. You can retrieve the ID of a request from the response of the GET endpoint described in Viewing Requests Pending Manual Approval.

curl --insecure -u <username>:<password> -X POST <REST-API-URL>/mgm/<MGM-HOLDING-ID>/approve/<REQUEST-ID>

To decline a request, pass the ID of the request and a reason to the POST method of the mgm/{holdingidentityshorthash}/decline/{requestid} endpoint. You can retrieve the ID of a request from the response of the GET endpoint described in Viewing Requests Pending Manual Approval.

curl --insecure -u <username>:<password> -d <REASON> <API-URL>/mgm/<MGM-HOLDING-ID>/decline/<REQUEST-ID>

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.