Connecting A Web Page To FileMaker, Step By Step

Overview

A web page cannot open a FileMaker file directly. It talks to FileMaker through the Data API, a set of web addresses that send and receive data. Here is what that conversation actually looks like.

Step one: ask for a token

The web page sends a username and password to FileMaker. FileMaker checks them and sends back a token. A token is a short code that proves who is asking.

The web page saves that token. It uses it for every call that follows. No password gets sent again after this.

Step two: ask for records

Now the web page calls the address for one layout, which is one specific view of the data. It attaches the token to prove it already logged in.

FileMaker sends back the records as JSON, a plain text format that most web tools already read. The web page reads that JSON and shows the records on screen.

Step three: close the session

When the web page is done, it sends one more request. This one cancels the token.

That step matters more than it sounds. Skip it and:

• the session stays open on the server
• it counts against your connection limit
• it sits there until it times out on its own
• a busy app can run out of sessions to hand out

Three calls, one login, one clean end. That is the whole shape of it.

Do you close your token every time, or let it time out on its own?