Capability sheet

Cority and Dojo360

What the Cority connector can read and write, how it authenticates, and the limits to plan around.

Cority
Book a demo View in the marketplace
Status
BetaDocs reviewed · Last reviewed 2026-10-20
Categories
Energy, Industrial Data & HSE
Industries
Energy, oil & gas, Manufacturing & industrial distribution, Construction & engineering, Fuel & convenience retail, Logistics & transport
Regions
GCC, India, Singapore, Malaysia, US, UK, EU & ANZ
API and auth
REST API · OAuth 2.0
Dojo360 can pull
  • Tags and readings
  • Incidents
  • Audits
  • Actions
Dojo360 can push
  • Incidents
  • Actions
Webhooks
No. Changes are picked up on a schedule.
Sandbox
Available
Key limits
  • API documentation is provided to licensed customers; scope not confirmed.
  • Process historians are often customer-hosted and require a secure network connection.
  • No webhooks; changes are picked up on a scheduled sync.
Access requirements
  • Admin access to the client account to authorize the connection.
  • Plan or partner requirements to be confirmed with the vendor during onboarding.
Cority developer documentation

Cority 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