PUT

Verify Enrollment SMS, Email, Protect, Authenticator

Use this API to verify enrollment for OneLogin SMS, OneLogin Email, OneLogin Protect and Authenticator authentication factors. At this point, the enrollment of the factor should have already been requested, and this API will allow you to verify the OTP code sent to or generated for the user on the provided factor. The status of the registration should be pending. If the initial registration was completed with veriifed = True then this step will not be necessary.

The API supports enrollment for SMS, Email, Google Authenticator, and OneLogin Protect. Other factors can be enrolled manually by the user. Duo is supported for OTP factors, but registration isn’t supported.

Resource URL

https://<subdomain>.onelogin.com/api/2/mfa/users/<user_id>/registrations/<registration_id>

Header Parameter

Authorization

required

string

Set to bearer:<access_token>.

Set <access_token> to the access token you generated using the Generate Token API.

The access token must have been generated using an API credential pair created using the scope required to call this API. This API can be called using the Manage All scope.

Resource Parameter

user_id

required

integer

Set to the id of the user.

If you don't know the user's id, use the Get Users API call to return all users and their id values.

registration_id

required

uuid

Set to the uuid of the registration. This was included in the response as part of the initial request in Enroll Factor.

Request Parameters

otp

required

integer

One-Time-Password (OTP) that was sent to the user based on the chosen factor. OneLogin SMS and OneLogin Email support this OTP code.

Request Body

{
    "otp": 58959
}

Sample Responses

OneLogin SMS, OneLogin Email, Authenticator

[
  {
      "id": "406fefd4-8a36-4aee-880c-f3e4a928e27d",
      "status": "accepted",
      "device_id": "3919988"
  }
]
{
    "statusCode": 401,
    "name": "InvalidCredentials",
    "message": "Please provide valid credentials"
}
```json

</div>
</div>


<h2>Response Elements</h2>
<table width="86%" cellpadding="10">
  <tbody>
        <tr>
        <td valign="top" style="text-align: right"><code>id</code></td>
        <td valign="top">Registration identifier. </td>
      </tr>
      <tr>
        <td valign="top" style="text-align: right"><code>status</code></td>
        <td valign="top"><code>pending</code> registration has not been completed successfully.  <code>accepted</code> registration has successfully completed. </td>
      </tr>
      <tr>
        <td valign="top" style="text-align: right"><code>device_id</code></td>
        <td valign="top">Device id to be used with <a href="/api-docs/2/multi-factor-authentication/verify-factor">Verify the Factor</a>.</td>
      </tr>
      
  </tbody>
</table>

<h2 id="postman-collection">Postman Collection</h2>

[<img src=https://run.pstmn.io/button.svg alt="Run In Postman" style="width: 128px; height: 32px;">](https://god.gw.postman.com/run-collection/2629710-07192ad9-633a-4583-a9d1-47bc89c8c91d?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D2629710-07192ad9-633a-4583-a9d1-47bc89c8c91d%26entityType%3Dcollection%26workspaceId%3D2a9bbc3a-4259-4faf-9f51-0b7ca1df3fd0)

<h2>Sample Code</h2>
<h3 id="sample-curl-request">cURL</h3>
<p>Replace sample values indicated by <code>&lt; &gt;</code> with your actual values.</p>

<pre><code class="prettyprint lang-c">curl 'https://&lt;subdomain&gt;.onelogin.com/api/2/mfa/users/&lt;user_id&gt;/registrations/&lt;registration_id&gt;' \
-X PUT \
-H "Authorization: bearer &lt;access_token&gt;" \
-H "Content-Type: application/json" \
-d '{
  "otp":123456
}'</code>
</pre>