In that case then you need to look at an API gateway type service. Security - if at all possible you probably don’t want to expose your FileMaker server to the internet. Keep calculations to a minimum and serve only the fields and data you need on the front end. REST layouts - I would recommend building layouts that are specifically for the API to serve from. Donut think FileMaker scales in this situation particularly well. But even still, our traffic would most likely be way less than a website. Speed - I’ve been pleasantly surprised by the speed of our app, but we’re currently just in a dev environment.

There are libraries to access from server side (ie NodeJs) but nothing from the browser. Normally I would reach for a library to handle this but haven’t found one yet. Claris is definitely spending a lot of effort on the data api to make it the primary way data goes in or out of FileMaker.Īuthentication - You will need to authenticate in order to pull data from FileMaker data API.

Tldr FileMaker Data API is the modern way to get data in or out of FileMakerįileMaker Data API - ODBC is not an option for accessing data from a web client.

It’s definitely possible but a lot of different angles to consider:

Filemaker pro database extractor