# List Unverified Contacts

Returns a list of contacts, related to domains within your account, that require verification as per ICANN procedures.
When a new domain is created, unverified contacts are not immediately available in API responses.  Records are added by a scheduled process that runs approximately every 10 minutes.  As a result, there may be up to a 10-minute delay before unverified contacts appear in the API. This delay also applies to related events such as webhooks or other downstream systems that depend on contact verification data. 
This API is only available to approved reseller accounts. Contact name.com support to request access.

Endpoint: GET /core/v1/contacts/unverified
Version: 1.8.2
Security: BasicAuth

## Query parameters:

  - `perPage` (integer)
    PerPage is the number of records to return per request. If not passed in the request, the default value is 100 records.
    Example: 100

  - `page` (integer)
    Page is which page to return. If not passed in the request, the default page is 1.
    Example: 2

## Response 200 fields (application/json):

  - `unverifiedContacts` (array, required)

  - `unverifiedContacts.verificationId` (number, required)
    The id of the verification record for the contact. Please note, this is different than the contact_id that may be returned in other API contexts. This id specifically relates to the verification and will be different than an contact_id for the same contact record in other contexts.
    Example: 4897668

  - `unverifiedContacts.createDate` (string, required)
    The date the record requiring verification was created.
    Example: "2025-01-01T15:35:06Z"

  - `unverifiedContacts.verifyBy` (string, required)
    The date/time that the contact record must be verified by.  If the contact record is not verified by this date, the domain may become locked by the registry. This is typically 15 days from the creation date of the verification record, but may vary by TLD and registry.
    Example: "2025-01-16T15:35:06Z"

  - `unverifiedContacts.email` (string, required)
    The email address of the contact to be verified. This is the primary identifier used for verification.
    Example: "admin@example.com"

  - `unverifiedContacts.domains` (array, required)
    A list of the domains that the contact verification record is applied to.

  - `from` (integer, required)
    From is the starting record for the current page.
    Example: 1

  - `to` (integer, required)
    To is the ending record for the current page.
    Example: 25

  - `lastPage` (integer, required)
    LastPage is the identifier for the final page of results. This value will be null if there is not a previous result page.

  - `nextPage` (integer,null, required)
    NextPage is the identifier for the next page of results. This value will be null if there is not a next page of results.

  - `totalCount` (integer, required)
    TotalCount is total number of domains returned for request.

## Response 401 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Unauthorized"

## Response 403 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Permission denied"

  - `details` (string,null)
    Additional context or information about the error
    Example: "Failed authentication"

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Rate Limit Exceeded"

## Response 500 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."