---
title: Device custom verification URIs
description: "Device authorization applications in PingOne can use a device custom verification URI to present a shorter URL that's easier for the user to enter."
component: pingone
page_id: pingone:applications:p1_device_custom_verification_uris
canonical_url: https://docs.pingidentity.com/pingone/applications/p1_device_custom_verification_uris.html
revdate: February 10, 2025
section_ids:
  related-links: Related links
---

# Device custom verification URIs

Device authorization applications can use a device custom verification URI to present a shorter URL that's easier for the user to enter.

|   |                                                                                                                                                                                    |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Device custom verification URIs can be configured for applications for which the **Device Authorization** grant type is enabled. Learn more in [Grant types](p1_grant_types.html). |

Instead of presenting the user with a PingOne URL, such as https\://auth.pingone.com/device/082dba86-d36e-413e-85b4-ee499a5cea55, a device custom verification URI provides them with a shorter URL that's easier to enter or remember (for example, https\://example.com/device).

When you configure your device authorization application in PingOne, you can define this URI using the **Device Custom Verification URI** setting. If you configure the **Device Custom Verification URI** setting, the response from PingOne returns the URL as configured. If you do not use this setting, the generated device custom verification URI follows these rules:

**Response URL formats**

| Custom domain configured for the environment? | Device path ID configured? | Format of URL returned from PingOne                                                                                                                                                                                              |
| --------------------------------------------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Yes                                           | Yes                        | The URL returned by PingOne is in one of the following formats:- https\://\<customDomain>/device/\<devicePathId>

- https\://\<customDomain>/device/\<devicePathId>?user\_code=\<userCode>                                       |
| Yes                                           | No                         | The URL returned by PingOne in one of the following formats:- https\://\<customDomain>/device

- https\://\<customDomain>/device?user\_code=\<userCode>                                                                          |
| No                                            | Yes                        | The URL returned by PingOne is in one of the following formats:- https\://auth.pingone.\<geography>/\<envId>/device/\<devicePathId>

- https\://auth.pingone.\<geography>/\<envId>/device/\<devicePathId>?user\_code=\<userCode> |

|   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | The URLs for the device custom verification URI and for the redirect are generated based on the inbound initial authorize call. Learn more in [Configuring a redirect for a device custom verification URI](p1_configure_redirect_device_custom_verification_uri.html).For example, if the custom domain for the environment is example.com, but the initial call is from https\://auth.pingone.com/\<envID>/as/device\_authorization, then the generated device custom verification URI will have a format of https\://auth.pingone.com/\<envId>/device/\<devicePathId>.If the initial call is from https\://example.com/as/device\_authorization, the generated device custom verification URI will have a format of https\://example.com/device/\<devicePathId>. |

## Related links

* [Editing an application - Device authorization](p1_edit_application_device_auth.html)