Advanced Admin API: automating FileMaker Server deployments
ExpertUse the Admin API to build deployment automation — upload databases, push configuration changes, and orchestrate server operations from CI/CD pipelines.
What you'll learn
- How to upload a database file to FileMaker Server via the Admin API
- How to build a safe database swap automation
- How to call the Admin API from a FileMaker script using Insert from URL
The FileMaker Admin API goes beyond manual management. Combined with scripting (bash, Python, or FileMaker itself), it enables fully automated deployment pipelines: upload a new database, close the old one, open the new one, verify, and notify — all without touching Admin Console.
1/3
1
Upload a database file via the Admin API
The Admin API accepts multipart file uploads to host a new database. This enables CI/CD pipelines to push new database versions automatically.
TEXT
# Upload a database file to FileMaker Server curl -X POST \ "https://[host]/fmi/admin/api/v2/databases" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: multipart/form-data" \ -F "upload=@/path/to/NewDatabase.fmp12" \ -F "key=" \ -F "fmpath=" # The file appears in the Databases list as Closed # Open it with a PATCH after upload
FileMaker Server on Linux: deployment, monitoring, and systemdHigh availability and disaster recovery for FileMaker Server
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo