---
sourceDocument: Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-asset-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Configure the Lenovo Warranty API connection

# Connect to the Lenovo Warranty API {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create a connection and credential to connect to the Lenovo Warranty API and download the warranty information for hardware assets.

## Before you begin

You should have the Client ID provided by Lenovo. If you don't have one, contact your organization's Lenovo sales or service representative.

Role required: admin

## Procedure

1. Navigate to AllConnections \& CredentialsConnection \& Credential Aliases.
2. Select Lenovo.
3. From the Related Links, select Create New Connection and Credential.
4. **Optional:** Change the default connection name for the connection to the Lenovo Warranty API In the Connection Name field.  
   By default, this field is set to Lenovo Connection.  
   Important:  
   Don't change the default URL specified in the Connection URL field.
5. In the Client ID field, enter the Client ID provided by Lenovo.
6. Select Create.

## Result

The Lenovo connection is successfully created and listed in the Connections tab.

## What to do next

After you save the connection and credential records, the Lenovo Warranty API is ready to use. For information about the process for downloading warranty information for hardware assets, see [Integration with Lenovo for asset warranty details](https://www.servicenow.com/docs/xmy7gxttnkYCeAdXQMgCnQ "The Lenovo Asset Warranty Flow enables you to get the warranty information of hardware assets by connecting to the Lenovo Warranty API.").  
Tip:  
No connection test is available for the Lenovo Warranty API. To confirm that the connection is working, check the Asset Job Log \[asset_job_log\] table after the warranty download job runs. If the credentials are incorrect or the connection fails, the job runs but doesn't download warranty information, and logs the details for each run.

*[\>]: and then