Capability sheet
Eptura and DojoCOMMAND
What the Eptura 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 · API key
- DojoCOMMAND can pull
- Sites
- Service requests
- SLAs
- Contracts
- DojoCOMMAND can push
- Service requests
- Comments
- Webhooks
- Yes
- Sandbox
- Available
- Key limits
- API availability differs across Eptura products.
- 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.
Eptura is a trademark of its owner and is used here for identification only. See third-party trademarks.
One hub
Ready to run it as one operation?
Pick the native apps you need, connect the ones you already have, and see your DojoCOMMAND price live. Or start with a fixed-price Blueprint and we'll map it for you.