Warranty tracking

Set warranty expiry dates on assets and Tether surfaces anything expiring soon on the dashboard — so nothing slips through unnoticed.

Setting a warranty expiry date

The warranty_expiry field is available on every asset. Set it in three ways:

• Create/edit form — enter the date in the Warranty Expiry field
• CSV import — include a warranty_expiry column. Accepted formats: YYYY-MM-DD, MM/DD/YYYY, DD/MM/YYYY
• API — set "warranty_expiry": "2027-03-01" in a create or update request

Dashboard display

The dashboard surfaces warranty expiry information at two levels:

Client dashboard

When logged into a client portal, the dashboard shows a list of assets whose warranty_expiry date falls within the next 30 days. Assets are sorted by expiry date, closest first. The expiry date is highlighted in amber.

MSP dashboard

The MSP-level dashboard shows an Expiring Soon stat card with the total count of assets expiring within 30 days across all tenants. The per-client breakdown in the Clients table also shows a count for each client.

Recommended warranty workflow

A practical approach for MSPs:

1. On asset import — always include warranty_expiry in your CSV. If you don't know the exact date, check the manufacturer website or the original invoice.
2. Weekly dashboard check — MSP admins should check the Expiring Soon card on the MSP dashboard every Monday
3. 30 days out — contact the manufacturer or reseller to arrange renewal or replacement
4. At expiry — update the warranty_expiry field with the new expiry date, or leave it and the item will drop off the warning list automatically

Assets with no warranty expiry

Assets with a blank warranty_expiry field are never shown in the expiring dashboard — only assets with a date set that falls within 30 days appear. Peripherals, consumables, or fully owned equipment that carries no warranty can safely have the field left blank.

Querying warranty data via the API

httpCopy
# Get all assets expiring within 30 days
GET /api/assets?warranty_expiring=30
Authorization: Bearer {token}

# The dashboard stats endpoint also includes a count:
GET /api/dashboard/stats
Authorization: Bearer {token}
# Response includes: "expiring_soon": 3