Capability sheet
Planon and Dojo360
What the Planon connector can read and write, how it authenticates, and the limits to plan around.
- Status
- BetaDocs reviewed · Last reviewed 2026-10-20
- Categories
- Facilities Management
- Industries
- Facilities management, Real estate developers & brokerages, Healthcare providers, Hotels, restaurants & hospitality groups, Private school groups & universities, Retail & e-commerce, Manufacturing & industrial distribution
- Regions
- GCC, India, Singapore, Malaysia, US, UK, EU & ANZ
- API and auth
- REST API · Mixed
- Dojo360 can pull
- Sites
- Service requests
- SLAs
- Contracts
- Dojo360 can push
- Service requests
- Comments
- Webhooks
- Yes
- Sandbox
- Available
- Key limits
- API documentation is provided to licensed customers; scope not confirmed.
- Available objects depend on the modules licensed by the client.
- Access requirements
- Admin access to the client account to authorize the connection.
- Plan or partner requirements to be confirmed with the vendor during onboarding.
Planon is a trademark of its owner and is used here for identification only. See third-party trademarks.
Stop running six islands
Ready to run it as one operation?
Start with a fixed-price Blueprint. We map every system you run, where work is done twice, and what your Dojo connects first.
Works with the systems you already run