CloudRadial pulls warranty dates from Dell, Lenovo, and supported PSAs automatically, but sometimes the date doesn't show up the way you expect — maybe it's stale, missing, or the vendor didn't answer on the first try. There are two ways to fix it:
- Trigger a warranty refresh — ask CloudRadial to re-query the vendor. Start here for Dell, Lenovo, or any vendor that supports automatic lookups
- Manually update the warranty date — set the date yourself. Use this for HP, Microsoft Surface, and anything else that doesn't support automatic lookups
Both go through the CloudRadial v2 API. The easiest way is Swagger UI at https://api.us.cloudradial.com/swagger, which handles auth and request formatting for you.
- Before You Begin
- Authenticate in Swagger UI
- Trigger a Warranty Refresh
- If You Don't Have the Serial Number
- Response and Verification
- Troubleshooting
- Manually Update the Warranty Date
Before You Begin
You'll need:
- A CloudRadial API key pair (public and private key). If you don't already have one, generate a pair under Partner > Settings > Integrations > API (Beta) > +Add API Keys
- The endpoint's serial number, or alternatively the manufacturer and machine name
- Access to Swagger UI at
https://api.us.cloudradial.com/swagger
Authenticate in Swagger UI
Click Authorize at the top of the Swagger UI page. Enter your public key as the username and your private key as the password. That's it for the session — Swagger handles the Basic auth encoding and includes the header on every request.
Trigger a Warranty Refresh
Scroll down to the Endpoint section and find POST /v2/endpoint/{serialNumber}/update-warranty. Click Try it out, paste in the endpoint's serial number, and click Execute. No request body needed.
That kicks off an asynchronous job that re-queries the vendor for fresh warranty info. Give it a few minutes to run.
If You Don't Have the Serial Number
Use POST /v2/endpoint/{manufacturer}/{machineName}/update-warranty instead. Same async warranty lookup, just identified by manufacturer and machine name rather than serial.
Response and Verification
You'll get back HTTP 204 No Content, which means the job was accepted — not that it's finished. Give it a few minutes, then verify in the portal: Partner > Clients > [Client Name] > Impersonate Admin All Features > Infrastructure > Endpoints. Open the specific device and check the warranty date under the Configuration tab.
Every API response also includes an x-documentation-url header with a link to the request log. If something doesn't look right, that's the fastest way to find out what happened.
Troubleshooting
401 Unauthorized — the API key pair is wrong, inactive, or not formatted correctly for Basic auth.
404 Not Found — the serial number, or manufacturer and machine name combination, doesn't match an endpoint in your tenant.
204 but the warranty never populates — the vendor probably doesn't support automatic lookups. HP and Microsoft Surface both stopped allowing this, so warranties on those need to be set manually (see the next section).
The x-documentation-url header on any response links straight to the request log and is the best starting point for debugging anything unexpected.
Manually Update the Warranty Date
For endpoints whose warranty can't be fetched automatically — HP, Microsoft Surface, and anything else not supported — set the expiration date directly on the endpoint record. The field is expirationDate, which is what the warranty report and dashboard chart both read from.
Use PATCH /v2/endpoint/{serialNumber} to update it. PATCH here uses the JSON Patch format (RFC 6902), so the body is an array of operations rather than a plain object. In Swagger UI, expand the PATCH operation, click Try it out, enter the serial number, and paste a body like the one below — replacing the date with the actual warranty expiration for that endpoint:
[
{ "op": "replace", "path": "/expirationDate", "value": "2027-03-15T00:00:00Z" }
]You'll get back a 204 No Content, and the updated date shows up immediately in the endpoint detail view and in warranty reports.
The same PATCH is also available at PATCH /v2/endpoint/{manufacturer}/{machineName} and PATCH /v2/endpoint/id/{endpointId} if a different lookup key is more convenient.
If you are still having trouble, we're here to help! Submit a ticket here for assistance, and don't forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.