How a FileMaker Data API call is processed

FileMaker Data API architecture diagram
FileMaker Data API architecture

  1. A REST API client sends a FileMaker Data API call (HTTPS request) to the web server over the HTTPS port (port 443). FileMaker Pro does not need to be installed or running.

  2. The web server routes the request through the FileMaker Web Server Module to the FileMaker Data API Engine.

  3. The FileMaker Data API Engine converts the HTTPS request (URL and JSON data) into a format that the Database Server component can understand, and requests data from the database hosted by the Database Server.

    The FileMaker Data API Engine requires that ports 3000 and 8989 be available.

  4. The Database Server sends the requested FileMaker data back to the FileMaker Data API Engine.

    The Database Server requires that port 5003 be available.

  5. The FileMaker Data API Engine converts the FileMaker data into an HTTPS response (URL with JSON data) to respond to the call, passing the data back to the web server.

  6. The web server sends the HTTPS response to the requesting REST API client.