MaintenanceTech by K3YHOLD
MaintenanceTech API
Developer documentation for connecting systems, workflows and applications to MaintenanceTech is coming soon. There is no public API today, and nothing on this page describes one.
What to expect
Planned documentation may include…
These are the chapters a reference tends to need. They are what we intend to write, not a description of what the platform exposes — when a section is real, it will say what it does and carry examples that run.
01
API reference
The resources the platform exposes, once there is a public surface to document.
Planned
02
Authentication
How an application would identify itself, and what an integrator is responsible for.
Planned
03
Events and webhooks
How a system could be told that something changed, rather than polling for it.
Planned
04
Integration guides
Walkthroughs for the shapes of integration we see most often.
Planned
05
Examples
Working samples, written against the documented surface rather than ahead of it.
Planned
06
Implementation guidance
The operational side: environments, change, and what to do when something is wrong.
Planned
Nothing above is a commitment to a particular endpoint, authentication method, schema, event or limit. We would rather publish a page that says so than a page of plausible-looking syntax.
Building something that would talk to it?
Tell us what you would want to connect and what you would want back. The people we hear from now are the reason a documented surface ends up shaped like the work rather than like our database.
Meanwhile
MaintenanceTech works alongside the property software you already run by handing information off as an exported file today. That, and everything else, is on the platform’s own capability table — labelled with what works now and what is still coming.
The platform it will document.
MaintenanceTech runs the maintenance loop by phone, in two offerings — for owner-operators and for property managers.