Claris FileMaker Admin API

Name: Claris FileMaker Admin API API
Brand: Claris FileMaker Admin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybasic, bearer22 EndpointsREST

For Agents

Administer FileMaker Server and FileMaker Cloud — open and close databases, message connected clients, manage schedules, and inspect server status — through a JSON REST API.

Connect the Claris FileMaker Admin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Claris FileMaker Admin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Claris FileMaker Admin API API.

Exchange admin credentials for a bearer access token via POST /user/auth

Inspect FileMaker Server runtime status and metadata for health checks

Open, close, pause, and resume hosted databases without using the admin console

Send targeted messages to connected FileMaker clients before disconnecting them

GET STARTED

Start building with Claris FileMaker Admin API API

Explore with Jentic

View OpenAPI Document

Use for: I need to open a hosted FileMaker database programmatically, I want to message all connected clients before maintenance, List all databases currently hosted on this FileMaker Server, Get the current FileMaker Server status and uptime

Not supported: Does not read or write FileMaker records, run finds, or execute layout scripts — use the FileMaker Data API for record-level work and this Admin API for server, database, schedule, and client administration only.

Jentic publishes the only available OpenAPI document for Claris FileMaker Admin API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Claris FileMaker Admin API, keeping it validated and agent-ready. The FileMaker Admin API v2 is a REST API that performs administrative tasks on FileMaker Cloud and FileMaker Server, including server status checks, database lifecycle operations, schedule management, client session control, and runtime settings. Operators use it to script database opens and closes, push targeted messages to connected clients, and run backups on a schedule. Responses are JSON and authentication is performed by exchanging Basic credentials for a bearer access token.

Use Cases

Patterns agents use Claris FileMaker Admin API API for, with concrete tasks.

★ Automated FileMaker Server Health Checks

Operators can poll GET /server/status and GET /server/metadata on a schedule to feed monitoring dashboards or alerting systems with live FileMaker Server health. Combined with the databases endpoints, the same job can verify that critical solutions are open and accepting connections. This replaces manual logins to the admin console for routine checks.

GET /server/status and GET /databases, then alert if any expected database is not in the open state.

Maintenance Window Client Notifications

Before pushing a schema update or restarting the server, an admin can iterate connected clients via GET /clients and send a notice through POST /clients/{clientId}/message so users save their work. Once the window opens, DELETE /clients/{clientId} disconnects remaining sessions cleanly. This avoids data loss and surprise disconnects during maintenance.

GET /clients, POST /clients/{clientId}/message with the maintenance notice, wait, then DELETE /clients/{clientId} for any remaining sessions.

Scheduled Database Backups

Backup jobs can be created and inspected through the /schedules endpoints, letting infra teams version-control their FileMaker schedules alongside other infrastructure. The same endpoints expose schedule run results so a CI job can fail loudly when a backup did not execute. This keeps FileMaker administration in line with modern devops workflows.

POST /schedules with a nightly backup definition, then GET /schedules/{scheduleId} the next morning to confirm it ran.

AI Agent Driven Server Operations

An AI agent acting as a tier-1 ops responder can use Jentic to call the FileMaker Admin API when an alert fires: open a database that closed unexpectedly, message stuck clients, or roll a schedule. Credentials stay in the Jentic vault and the agent works from declared schemas, so it cannot drift onto undocumented endpoints. This is well suited to small operations teams stretching coverage hours.

Search Jentic for 'open a filemaker database', load the PATCH /databases/{databaseId} schema, and execute with action=open.

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for claris filemaker admin api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/user/auth

Request a bearer access token

GET

/server/status

Get FileMaker Server status

GET

/databases

List hosted databases

PATCH

/databases/{databaseId}

Open, close, pause, or resume a database

POST

/clients/{clientId}/message

Send a message to a connected client

DELETE

/clients/{clientId}

Disconnect a connected client

POST

/schedules

Create a scheduled task

POST

/user/auth

Request a bearer access token

GET

/server/status

Get FileMaker Server status

GET

/databases

List hosted databases

PATCH

/databases/{databaseId}

Open, close, pause, or resume a database

POST

/clients/{clientId}/message

Send a message to a connected client

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

FileMaker admin credentials and short-lived bearer tokens are stored in the Jentic vault. Agents trigger /user/auth through Jentic without ever seeing the raw username and password.

Intent-based discovery

Agents search by intent (e.g., 'open a filemaker database') and Jentic returns the matching Admin API operation with its input schema, so the agent does not need to read the FileMaker admin guide.

Time to first call

Direct FileMaker Admin API integration: 1-2 days for auth flow and database action mapping. Through Jentic: well under an hour to search, load, and execute the first administrative call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Claris FileMaker Data API

Record-level read/write counterpart to the admin API

Use the Admin API for server and database lifecycle; switch to the Data API when the agent needs to read or write actual records.

Complementary

Claris FileMaker OData API

OData 4.01 query interface for FileMaker data

Pair the Admin API for ops with the OData API when the agent prefers standard OData queries over the FileMaker Data API.

Alternative

MongoDB Atlas Admin API

Admin API for managed MongoDB clusters

Choose MongoDB Atlas when the workload is document-store; choose FileMaker Admin when the team is on FileMaker Server or Cloud.

FAQs

Specific to using Claris FileMaker Admin API API through Jentic.

Why is there no official OpenAPI spec for Claris FileMaker Admin API?

Claris does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Claris FileMaker Admin API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the FileMaker Admin API use?

The API uses HTTP Basic authentication on POST /user/auth to obtain a bearer access token, which is then sent as Authorization: Bearer {token} on subsequent calls. Tokens expire and must be refreshed by re-authenticating. Jentic stores the admin credentials in its vault and injects the bearer token at execution time.

Can I open and close hosted databases with the FileMaker Admin API?

Yes. PATCH /databases/{databaseId} accepts open, close, pause, and resume actions on a specific hosted database. DELETE /databases/{databaseId} removes the database from the host entirely.

What are the rate limits for the FileMaker Admin API?

Claris does not document a public rate limit table for the Admin API. Because operations are administrative (start, stop, schedule), volumes are typically low. Avoid tight polling of GET /server/status — refresh on a schedule of a minute or more.

How do I disconnect a stuck client through Jentic?

Search Jentic for 'disconnect a filemaker client', load the DELETE /clients/{clientId} schema, and execute with the clientId. Jentic supplies the bearer token from the vault.

Can the API manage scheduled backups?

Yes. POST /schedules creates a new schedule and GET /schedules lists existing ones. GET /schedules/{scheduleId} returns the configuration and last-run status for a specific schedule, so a job runner can verify a nightly backup actually ran.