Open Fasap

Connect Open Fasap to KODE OS for work orders data integration

Overview

Use this integration to connect Open Fasap to KODE OS. You can collect sensor and non-sensor work order data over REST with hybrid snapshot collection and use supported connector actions from Data Sources.

Property	Value
System Type	Work Orders
Communication	REST
Collection	Hybrid (Pull + Push)
Collection Mode	SNAPSHOT
Actions	Supported

Supported Capabilities

Collect Sensor Data
Collect Non-Sensor Data

Prerequisites

An active account with Open Fasap and access to their API or developer portal
OAuth client credentials (Client ID and Client Secret) from the Open Fasap developer portal
KODE OS environment with access to Data Sources

Generate API Credentials

Log in to the Open Fasap developer portal or admin console
Navigate to the API or developer settings section
Create a new API application or client
Note the Client ID and Client Secret — you will need these when configuring the connector in KODE OS

Configure Connector in KODE OS

Navigate to Data Sources in your building
Click API Catalog and search for Open Fasap
Click + Add Datasource
Fill in the fields below and complete the three-page setup flow

Field	Required	Type	Description
URL	Yes	text	The base URL or IP address of the external system
Client ID	Yes	password	The OAuth client ID from the vendor’s developer portal
Client Secret	Yes	password	The OAuth client secret from the vendor’s developer portal
Username	Yes	password	The username for authenticating with the external system
Password	Yes	password	The password for authenticating with the external system
Site ID	Yes	password	The site identifier in the external system
API Building ID	Yes	password	The building or source identifier in the external system
Contract ID	Yes	password	The contract identifier in the external system
Contract Number	Yes	password	The contract or service agreement number

Devices and Points

Point	Display Name
`New`	New
`FM_Criticity__c`	FM Criticity c
`FM_Comment__c`	FM Comment c
`FM_StartDate__c`	FM StartDate c

What Data You Get

Work Orders

Maintenance and service requests including title, description, status, priority, assignee, due dates, vendor response, resolution details, and cost estimates KODE OS maps Open Fasap data to these standard fields:

KODE Field	Source Field	Notes
id	`id`	—
woNumber	`caseNumber`	—
description	`description`	—
status	`status`	—
priority	`PRIORITY_CONSTANTS.get(priority`	—
category	`type`	—
subCategory	`object`	—
location	`location.name`	transformed
createdAt	`createdAt`	transformed
updatedAt	`modifiedAt`	transformed
startedAt	`startedAt`	transformed
lastComment	`comment`	—
assetName	`asset.name`	transformed
customFields	`(custom fields)`	custom fields object
id	`id`	—
woNumber	`workOrderNumber`	—
description	`description`	—
status	`status`	—
priority	`PRIORITY_CONSTANTS.get(priority`	—
category	`type`	—
subCategory	`subject`	—
location	`location.name`	transformed
createdAt	`createdAt`	transformed
updatedAt	`updatedAt`	transformed
dueDate	`dueDate`	transformed
completedAt	`endedAt`	transformed
duration	`completionTimeInMinutes`	—
serviceProvider	`serviceProvider`	—
lastComment	`lastComment`	—
assetName	`asset.name`	transformed
customFields	`(custom fields)`	custom fields object

Polling Schedule

WorkOrder — Default polling: 30 minutes (min: 30 minutes, max: 1 days)

For more details on collection modes, see the Data Collection guide.

Available Actions

Create Case

Type: Write Creates a new maintenance case in OpenFASAP

Field	Type	Required	Input	Options / Default
Description	STRING	Yes	Text Area	—
Problem Cause	STRING	Yes	Drop Down	Dynamic: fetched from OpenFASAP symptoms API
Location	STRING	No	Drop Down	Dynamic: fetched from OpenFASAP sites/buildings API
Equipment	STRING	No	Drop Down	Dynamic: fetched from OpenFASAP equipments API
Type	STRING	Yes	Drop Down	Static: type options
Priority	STRING	Yes	Drop Down	Static: priority options
Comment	STRING	No	Text Area	—
Start Date	DATE_TIME	No	Text Box	—

Example Request

{
  "description": "example-value",
  "problemCause": "example-value",
  "type": "type options",
  "priority": "priority options",
  "location": "example-value",
  "equipment": "example-value"
}

Expected Result

KODE OS sends the action to the external API using the configured connector credentials
The external system returns success (typically HTTP 2xx) and processes the requested operation

For more details on how actions work, see the Actions guide.

Use Cases

Once connected, this integration enables you to:

Centralize maintenance requests and work order status from facility management systems
Create and update work orders directly from KODE OS when issues are detected
Track maintenance KPIs including response time, completion rate, and cost

Troubleshooting

Authentication or connection error

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Ensure the Client ID and Client Secret match the values from the Open Fasap developer portal.

Data collection stops or gaps appear

Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Open Fasap API.

Get Started

Capabilities

All Integrations

Overview

Supported Capabilities

Prerequisites

Generate API Credentials

Configure Connector in KODE OS

Devices and Points

What Data You Get

Work Orders

Polling Schedule

Available Actions

Create Case

Example Request

Expected Result

Use Cases

Troubleshooting

​Overview

​Supported Capabilities

​Prerequisites

​Generate API Credentials

​Configure Connector in KODE OS

​Devices and Points

​What Data You Get

​Work Orders

​Polling Schedule

​Available Actions

​Create Case

​Example Request

​Expected Result

​Use Cases

​Troubleshooting

Overview

Supported Capabilities

Prerequisites

Generate API Credentials

Configure Connector in KODE OS

Devices and Points

What Data You Get

Work Orders

Polling Schedule

Available Actions

Create Case

Example Request

Expected Result

Use Cases

Troubleshooting