POST
Turn a reported fault into a work order
Takes a fault described the way a tenant actually describes it and returns the fields Archibus, SAP PM or your own CAFM system needs to open a ticket.

Priority and SLA

sla_hours always matches the priority, to the response times a Saudi facilities team actually works to. escalate is the signal to page someone rather than to queue the ticket. Wire it to whatever your out-of-hours process already is.

What the caller did not say

missing lists the fields your system will want that the report did not contain. On a live line, that is the list of things worth asking before hanging up. See Actions.

Writing it into your system

This endpoint produces the work order. Posting it into Archibus or SAP is an integration, connected during implementation. See Integrations.

Limits and cost

Text is truncated at 4,000 characters. Four cents a ticket.

Authorizations

Authorization
string
header
required

API token from the Voho console. Begins with voho_sk_live_.

Body

application/json
text
string
required
Example:

"There's a smell of burning on the fourth floor, near the east stairwell."

Response

The work order.

summary
string
asset
string
Example:

"AHU-04"

location
string
Example:

"Level 4, east stairwell"

trade
string
Example:

"HVAC"

priority
enum<string>
Available options:
emergency,
urgent,
routine
sla_hours
integer

Matches the priority: 1 for emergency, 8 for urgent, 72 for routine.

escalate
boolean
missing
string[]

What the caller did not say that the system will want.

cost_cents
integer

What this call cost, in cents. Also returned as the X-Voho-Cost-Cents header.