Introduction
Even though FME is a "no-code" platform, your FME workflows still be incorporated into scripted web development projects.
Many organizations use web applications for critical workflows like supporting public services, sharing important data and information, and supporting internal processes. The FME Flow REST API and Web Services can be seamlessly integrated into these projects using HTML, JavaScript, and CSS.
When to Use FME in Web Development?
Consider using FME in the following scenarios:
- Building a custom web application with FME functionality
- Extending, replacing, or transitioning existing custom applications with FME
- Building widgets in third-party web applications
- Automating and triggering FME workflows from scripted applications
- Replacing deprecated FME Server Javascript library (fmeserver.js) functionality
Otherwise, consider FME Flow Apps as a no-code solution for running FME Workspaces as web applications.
Terminology
- FME Flow REST API: Provides an underlying REST-based communication mechanism for client-service applications, and also serves as a REST API. The REST service supports response formats in JSON and XML. See Getting Started with the FME Flow REST API or the FME Flow REST API V4 Documentation
-
FME Flow Web Services: FME Flow web-based services that are designed to deliver data in a Service-Orientated Architecture (SOA)
- Transformation Services: Web Services that deliver data in different ways. See "Which FME Flow Service Should I Use?" for more information.
- Utility Services: Designed for programmatic access to FME Flow. Including the Data Upload Service.
- fmeserver.js: Deprecated Javascript library for FME. This library longer supported but may still be referenced in old tutorials and demos.
As of FME Flow 2025.1, the V3 REST API has been deprecated. The current API will remain accessible, but no new features or general bug fixes will be implemented. Starting with FME Flow 2026.1, the V3 API will be removed. We encourage all users to prepare their systems for this change.
The V4 REST API offers enhanced security and usability, including new and reorganized endpoints, as well as the removal of certain endpoints. For information on migrating from V3 to V4, please see the FME Flow REST API V4 documentation and click on the heading Migrating from REST API V4.
Articles
Building a Custom Web Form with FME Flow and JavaScript
This tutorial creates a basic, scripted web application that demonstrates API job submission to FME Flow. Uses the FME Flow REST API and Data Download Service with HTML, Javascript, CSS, and the FME Flow.
Spatial Dashboard Using WebSockets
This tutorial creates a basic HTML, Javascript, and CSS web map that receives WebSocket data from FME Flow.