FMS:Connect Systems

FMS:Connect Systems provides comprehensive facility management solutions that help organizations optimize building operations, maintenance workflows, and resource allocation through integrated management tools and real-time monitoring capabilities.

Power end-to-end data operations for your FMS:Connect Systems API with Nexla. Our bi-directional FMS:Connect Systems connector is purpose-built for FMS:Connect Systems, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to FMS:Connect Systems or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your FMS:Connect Systems workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a FMS:Connect Systems credential, you need to obtain a Client ID and Client Secret from your FMS:Connect Systems account. The Client ID and Client Secret are required to authenticate with the FMS:Connect Systems API.

To obtain your Client ID and Client Secret, you need to have a FMS:Connect Systems account with API access enabled. Once you have access to your account, you can generate a Client ID and Client Secret from your FMS:Connect Systems administration portal. The Client ID and Client Secret are used to obtain a bearer token for authentication with the FMS:Connect Systems API. The bearer token is sent in the Authorization header with the Bearer prefix for all API requests to the FMS:Connect Systems API. For detailed information about API authentication setup, refer to the FMS:Connect Systems documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	Yes	Client ID
Client Secret	Yes	Yes	Client Secret
Hostname	Yes	No	The hostname is the name of the client. This information is present as - https://<hostname>.fmshosted.com/fmsconnect/
Environment	Yes	No	Allowed values: Test (Establishes connectivity with Test Environment); Production (Establishes connectivity with Production Environment)

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – FMS:Connect Systems

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your FMS:Connect Systems Client ID in the Client ID field. This is the Client ID you obtained from your FMS:Connect Systems administration portal.

4. Enter your FMS:Connect Systems Client Secret in the Client Secret field. This is the Client Secret you obtained from your FMS:Connect Systems administration portal.

   Keep your Client ID and Client Secret secure and do not share them publicly. The Client ID and Client Secret provide access to your FMS:Connect Systems account and should be treated as sensitive information. You can view and manage your API credentials in your FMS:Connect Systems administration portal. The Client ID and Client Secret are used to obtain a bearer token for authentication with the FMS:Connect Systems API. For detailed information about obtaining and managing API credentials, see the FMS:Connect Systems documentation.

5. Enter your FMS:Connect Systems hostname in the Hostname field. This is the name of your client and is present in your FMS:Connect Systems URL as https://{hostname}.fmshosted.com/fmsconnect/. The hostname is used to construct the authentication and API endpoint URLs.

   The hostname is the name of your client and can be found in your FMS:Connect Systems URL. The hostname is used to construct the authentication and API endpoint URLs. For detailed information about determining your hostname, see the FMS:Connect Systems documentation.

6. Select the environment you want to connect to from the Environment dropdown menu. Available options are:

   • Test: Establishes connectivity with Test Environment
   • Production: Establishes connectivity with Production Environment
   The environment determines which FMS:Connect Systems environment you will connect to. Use the Test environment for development and testing purposes, and the Production environment for production data access. The environment is used to construct the authentication and API endpoint URLs. For detailed information about environment configuration, see the FMS:Connect Systems documentation.

7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the FMS:Connect Systems connector tile, then select the credential that will be used to connect to the FMS:Connect Systems instance, and click Next; or, create a new FMS:Connect Systems credential for use in this flow.

Manual configuration

FMS:Connect Systems sources are configured entirely through the Advanced tab, since FMS:Connect Systems does not expose pre-built endpoint templates. Select the method that will be used for calls to the FMS:Connect Systems API from the Method pulldown menu, then enter the URL of the FMS:Connect Systems API endpoint from which this source will fetch data in the Set API URL field. FMS:Connect Systems API endpoints typically follow the pattern https://{hostname}.fmshosted.com/{environment}/{endpoint_path}, where {hostname} is your Hostname and {environment} is your Environment from the credential configuration. Follow the instructions in Connect to Any API to configure date/time and lookup macros, path to data, metadata, and request headers.

The endpoint requires Bearer Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The bearer token is obtained using your Client ID and Client Secret. For detailed information about FMS:Connect Systems API endpoints and available APIs, see the FMS:Connect Systems documentation.

Once all of the relevant settings have been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched, and click the Create button in the upper right corner of the screen to save and create the new FMS:Connect Systems data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.