TL;DR: The Lexful API lets your existing tools — RMMs, PSAs, automation platforms — sync data into Lexful automatically. You don't need to be a developer to benefit. Most MSPs start with one integration and build from there.
What Is an API?
An API (Application Programming Interface) is a way for different software systems to share information automatically. Instead of a technician manually copying device details from your RMM into Lexful, an API integration does that transfer on its own — every time, without human effort.
💡 Tip: You don't need to be a developer to benefit from the Lexful API. Many integrations can be built using no-code tools like Rewst, Zapier, or Power Automate.
What Can the API Do for Your MSP?
Keep assets current automatically — your RMM syncs device info whenever assets change; your PSA creates client organizations when you sign new contracts.
Migrate from legacy platforms — bulk-import documentation, organizations, assets, passwords, and procedures from IT Glue, Hudu, or others.
Build custom workflows — trigger documentation creation based on events in other systems (new client signed, device deployed, technician onboarded).
Power internal tools — query Lexful from dashboards or internal apps to display documentation alongside tickets.
Core Concepts
Lexful's API is built around three concepts that mirror how MSPs already think about documentation.
Organizations An organization is a client — one of the companies you provide IT services to. Everything in Lexful is organized by client. When you sync from your PSA, each company becomes a Lexful organization.
Entities An entity is any individual item you document: servers, workstations, switches, contacts, procedures, passwords. Entities always belong to an organization — a server is always "Acme Corp's file server," not just "a file server."
Entity Types An entity type is a template that defines what fields you capture for a category of items. Your "Windows Server" type might include IP address, OS version, and backup schedule. When you create a new server entity, you're filling in that template.
📝 Note: These three concepts work together. "Acme Dental" (organization) contains their domain controller, firewall, and backup procedure (entities) — each based on an entity type that defines its structure.
Connecting Your Tools
The most common use of the API is keeping your existing MSP tools in sync with Lexful.
RMM tools (Datto RMM, NinjaRMM, ConnectWise Automate) — push device and asset info whenever your monitored environments change.
PSA tools (ConnectWise PSA, Autotask, HaloPSA) — sync client companies, contacts, and configuration items.
Identity providers (Microsoft Entra ID) — automatically provision and deprovision Lexful access as team members join or leave.
Automation platforms (Rewst, Power Automate, Zapier) — build workflows that create documentation based on events in other systems.
External IDs: Keeping Systems Linked
External IDs let you store a reference between Lexful and your other systems directly on each record. For example, when you sync a client from ConnectWise, you can store the ConnectWise company ID on the Lexful organization. When that client's info updates in ConnectWise, the integration knows exactly which Lexful record to update — no manual mapping, no duplicates.
Security and Access
Authentication: Every API request requires a valid API key, which can be created and revoked at any time in Settings.
Passwords stay encrypted: Credentials stored in Lexful remain encrypted. The API provides controlled access with logging for compliance.
Role-based access: API integrations respect the same permission model as the Lexful UI — Admin, Member, and Viewer roles determine what each integration can access.
How to Get Started
If you have a developer or technical resource: Point them to the full API reference at lexful.mintlify.app. It includes endpoint documentation, code examples, and technical specs.
If you're using an automation platform: Rewst (Lexful Connector), Power Automate (HTTP action), and Zapier (Webhooks + API calls) all connect to the Lexful API through their visual workflow builders — no code needed.
If you're working with a vendor or consultant: Share our API documentation and the "Integrate Your Tech Stack with Lexful" guide. They'll have everything they need to build your integration.
💡 Tip: Start with one integration that solves your most immediate pain point — usually RMM asset sync or PSA client sync. The value compounds as you add more over time.