Assets Guide

Look up the assets installed at a property and their warranty coverage

The Assets API returns the assets Sibi has on record for a property: what the product is, where it’s installed, its dimensions, and its warranty coverage.

Benefits

• Product identity: SKU, manufacturer, category, and serial number for each installed asset
• Warranty visibility: Time-sliced coverage windows so you can tell what’s covered and when
• Address-scoped: Narrow results to the assets installed at one property
• Single reads: Fetch one asset by its id once you hold it

Core Concepts

Asset ids

Every asset id this API returns carries the as_ prefix, so an id is self-describing wherever it is logged or stored. GET /assets/{id} accepts the id either way: as returned here (as_aBcD1234) or bare (aBcD1234), which is the form GraphQL responses and asset events carry.

Pagination

Results are paged with an opaque cursor. Pass the previous response’s next back as after to fetch the next page; next is null once a page comes back short.

Authentication

GET /assets and GET /assets/{id} require a Public REST API token that carries the read:assets scope. Create the token in the developer dashboard and grant it that scope, then send it as Authorization: Bearer <token>. A request with a token that lacks the scope receives a 403 with code INSUFFICIENT_SCOPE; a token issued for the GraphQL API receives a 403 with code REST_TOKEN_REQUIRED.

Next Steps

Endpoints