Track drying/mitigation equipment in Albi via the Asset API
domain: albi.readme.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an Albi API key and gather the equipmentTypeId, locationId, currentStaffId, and currentCompanyId values needed for the equipment record from Albi's Options endpoints.
Send a POST request to https://api.albiware.com/v5/Integrations/Asset/Equipment/Create with the API key in the header.
Include required fields: equipmentCustomId, equipmentTypeId, status, locationId, currentStaffId, and currentCompanyId.
If the equipment (e.g., an air mover or dehumidifier) is deployed to a specific job, include projectId to link it to that project.
For hardware vendors like Kahi that expect deduplication, also populate serialNo to avoid creating duplicate equipment records for the same physical unit.
Known gotchas
The API returns a 409 status specifically for equipment ID conflicts — check for this before assuming a general failure, since it indicates a duplicate equipmentCustomId or serialNo.
currentStaffId and currentCompanyId are both required even for equipment that isn't currently assigned to a job, which can be non-obvious when building bulk-import scripts.
Equipment records track custody/location, not real-time telemetry — Albi's Asset API is not a live IoT feed from moisture meters or drying equipment.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?