Versioned resources
Read overview, device, software, usage and license resources through stable /v1 contracts.
Customer API
Software inventory API and webhooks
Put Smantix's device, software and license data into the dashboards and reports your team already uses. Access is read-only, and webhooks let your systems react when something happens.
Read-onlyLimited to your workspaceSigned webhooks
{
"data": [
{ "id": "dev_01H", "host": "AVD-POOL-03", "role": "server", "hosting": "virtual",
"memoryMb": 65536, "lastSeen": "2026-11-06T08:12:00Z" },
{ "id": "dev_02H", "host": "SRV-FILE-02", "role": "server", "hosting": "virtual",
"memoryMb": 32768, "lastSeen": "2026-11-06T07:58:00Z" }
],
"nextCursor": "ZGV2XzAySA"
}For your developers
How the API works
Stable, tenant-scoped read-only endpoints. These are the details your developers will ask about.
Tenant-scoped keys
Create hashed access keys tied to one customer tenant and an explicit read scope.
Cursor pagination
Traverse large estates predictably without relying on unstable page offsets.
Quotas and audit
Apply request limits and retain credential issue, rotation and access events when the API is enabled.
Signed webhooks
Verify timestamped event signatures and rotate a tenant-specific delivery secret.
Retried delivery
A webhook delivery that fails with a temporary server error is retried.
Available resources
| Resource | Path | Returns |
|---|---|---|
| Devices | /v1/devices | Host, role, operating system and last seen |
| Software | /v1/software | Normalized titles and a device count |
| Licenses | /v1/licences | Purchased, assigned and installed quantities |
Usage is not a collection in the current API. Cursor pagination and signed webhooks are included. The reference for these paths is this page.
Connected estate
Use the same evidence in Smantix and your own systems
Show the same numbers in your own reports that your team sees in Smantix.