Introduction
The OttoFMS Developer API is a RESTful API that allows you to interact with your OttoFMS server and FileMaker Server.
Authentication
The OttoFMS Developer API uses the same authentication as the Claris FileMaker Server Admin API, so an Admin API token from FileMaker Server works here too.
The simpler option is an OttoFMS Admin API Key. Admin API Keys are long-lived, so you don't have to create and tear down an admin session for every call.
Pass the key as a bearer token in the Authorization header:
curl https://your.server.com/otto/api/info \
-H "Authorization: Bearer ak_123987"Every endpoint in this reference is authenticated the same way — the path and request body are unchanged, you just add the header.
Getting an Admin API Key
- Create one in the OttoFMS web console on the API Keys page, under the Admin API Keys tab. See the Using API Keys guide for step-by-step instructions.
- Or create one through this API with the Create an Admin API Key endpoint.
The same Admin API Key also authenticates the FileMaker Admin API proxy and the OttoFMS Admin MCP server.
An Admin API Key has the same power over your server as your Admin Console login. Treat it like a password and delete keys you are no longer using.
Looking for access to the data in your FileMaker files rather than to server administration? That's a Data API Key, used with the Data API proxy.
Was this page helpful?