FileMaker Cloud vs. On-Premise Data API differences

Expert

Understand the authentication and endpoint differences between FileMaker Cloud (Claris Cloud) and on-premise FileMaker Server.

What you'll learn

  • How Claris Cloud authentication differs from on-premise Basic Auth
  • The endpoint differences between Cloud and on-premise
  • How to write integrations that support both deployment targets

FileMaker Cloud (Claris Cloud) uses Claris ID (email/password or SSO) for authentication rather than FileMaker accounts. The Data API endpoint structure and most operations are the same, but the login flow and some configuration differences require separate handling in integrations that must work against both deployment types.

1/3
1

Authentication: Claris ID vs. FileMaker accounts

On-premise FileMaker Server: POST to /sessions with a Basic Auth header (base64-encoded username:password). FileMaker Cloud: use Claris ID token-based authentication. The most common approach for server-to-server is an API Key (FileMaker Cloud 1.19+).

HTTP
// On-premise: Basic Auth
POST /fmi/data/v1/databases/MyDB/sessions
Authorization: Basic base64(user:password)
Content-Type: application/json
Body: {}

// FileMaker Cloud: Claris ID Bearer token
POST /fmi/data/v2/databases/MyDB/sessions
Authorization: FMID <claris_id_token>
Content-Type: application/json
Body: {}
Bulk creates and updates via the Data APIRate limiting and retry strategies

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo