Reference · built on requestConnectorField service & CMMS

Corrigo Enterprise

Work orders, work zones, customers, spaces, and vendor invoices from Corrigo Enterprise through its Query and Command APIs.

Request accessPricing ↗

About

Corrigo Enterprise is the facilities work order platform from Corrigo, part of JLL Technologies, used by multi-site occupiers and property teams. It tracks WorkOrder records with their actions, priorities, flags, and notes, plus WorkZone buildings, Customer leases, Space, Contact, Location assets, ProcedureTemplate checklists, and WorkOrderCost vendor invoices. Its REST API has three endpoints per region: /api/v1/base for GET, POST, PUT, and DELETE, /api/v1/query for QueryExpression reads, and /api/v1/cmd for workflow commands.

Through Fibric, an operator polls WorkOrder by LastActionDateUtc or receives Corrigo Webhook events, then proposes WoCreateCommand, a status action such as Assign or OnHold, a WoNote, or an AP status change. You approve; the command runs once and leaves a record of what changed and why.

This is a reference listing. It documents what Fibric would read from Corrigo Enterprise and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • WorkOrder records with Number, StatusId, Priority, WorkZone, Employee, Specialty, DtDue, and LastAction through GET and POST /api/v1/query/WorkOrder
  • Work orders changed since a timestamp, by querying LastActionDateUtc with the GreaterOrEqual operator for event polling
  • Work Order Updates events such as Create, Pick Up, Start, Stop, On Hold, Complete, Cancel, and Assigned through the Corrigo Webhook
  • Work Order Estimate, Work Order Costs, Work Order Note, and Work Order Attachment events, signed with HMAC-SHA256 in X-Webhook-Signature
  • WorkZone, Customer, Contact, Space, Location, Document, and ProcedureTemplate entities through GET and QueryExpression
  • Vendor invoice state through WorkOrderCost.ApStatus, including the standard Submitted and Disputed statuses

Proposed actions

  • Target capability: propose a work order through POST /api/v1/cmd/WoCreateCommand, with WorkZone, Customer, and task references resolved first
  • Target capability: propose a work order action such as Assign, Pickup, Start, OnHold, Complete, Cancel, or Reopen through the WOActionType commands
  • Target capability: propose a WoNote on a work order, or a WoFlag, WoPriority, or WoOnSite change
  • Target capability: propose SendWorkOrderCommand so a connected Service Pro is notified of an assignment
  • Target capability: propose ApStatusChangeCommand to move a vendor invoice between AP statuses

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold vendors to the clock on open work orders

    DtDue, DtOnSiteBy, and DtAcknowledgeBy on each WorkOrder set the deadlines. When a Service Pro has not picked up in time, the operator proposes a reassignment or a flag for your approval.

    With Vendor SLA Watch

  • Find work orders nobody has touched

    A LastActionDateUtc query surfaces work orders with no action for days. The operator proposes an OnHold review or a reassignment and leaves the reason in a WoNote.

    With Work Order Aging

  • Send a tenant request to the right trade

    Requests arrive as WorkOrder records with a Specialty and TaskRefinement. The operator proposes the Employee or Service Pro to assign and the priority, then records the decision.

    With Request Routing

  • Check vendor invoices against completed work

    WorkOrderCost carries the invoice and its ApStatus. The operator compares it to the completed WorkOrder and its VendorNte, then proposes Submitted, Disputed, or a company-specific status through ApStatusChangeCommand.

    With Three-Way Match

Requirements

  • A Corrigo Enterprise service user in a role that includes Permissions - Web Services Access, normally the WSDK role
  • System Administrator access to Admin & Settings > Integration API Settings to generate the Client ID and Client Secret
  • A CompanyName header on every call, and a host name discovered through GetCompanyWsdkUrlCommand at the regional apilocator
  • API provisioning for the database and a Corrigo Sync subscription if you want the Corrigo Webhook; additional fees apply
  • A Stage or Preview company configured as a sandbox by your Corrigo System Administrator for testing
Authentication
OAuth 2.0 client credentials: a Client ID and Client Secret generated under Integration API Settings, posted to https://oauth-pro-v2.corrigo.com/OAuth/token for a bearer token that expires every 20 minutes.

Limits

  • No query may return more than 4000 entities in one operation; page with QueryExpression.Count and FirstResultIndex
  • Bearer tokens expire every 20 minutes and host names change without warning, so both are re-resolved together
  • WorkOrder, WorkZone, MaterialTransaction, Portfolio, WoVerification, WorkOrderCost, and AssetTree cannot be deleted through the API
  • The webhook is a separate Corrigo Sync product with its own fees; without it, change detection polls LastActionDateUtc

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Corrigo Enterprise ↗

Questions and answers

Does Corrigo Enterprise send webhooks?
Yes, through the Corrigo Webhook on the Corrigo Sync platform, which needs API provisioning and a Corrigo Sync subscription; additional fees apply. You pick event categories such as Work Order Updates, Estimate, Costs, Note, and Attachment, set a URL and a Signing Key, and each request carries an HMAC-SHA256 X-Webhook-Signature.
How do I find the API host name?
Call GetCompanyWsdkUrlCommand at the regional locator: am-apilocator.corrigo.com, apac-apilocator.corrigo.com, or emea-apilocator.corrigo.com. CommandResult.Url is the host for /api/v1/base, /api/v1/query, and /api/v1/cmd. Corrigo warns that host names change without warning, so do not hard-code them.
How are work order status changes made?
Not with PUT. Status changes are commands: the WOActionType values Assign, Pickup, Start, Stop, OnHold, Complete, Cancel, Reopen, CostStatus, and APInvStatus go through POST /api/v1/cmd. WoCreateCommand creates the work order, SendWorkOrderCommand notifies a connected Service Pro, and VerifyWorkCommand records the post-completion rating.
Ask about Corrigo Enterprise

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Corrigo Enterprise through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy