Developer platform: Read. Write. Automate.
Connect Filmo to the rest of your stack with the REST API, MCP and Workflows.
One API for your rental data.
Read orders and items, create contacts and keep another system in sync with a plain JSON REST API.
Keep another system up to date
Read updates with updatedAfter, and follow the sync guide for pagination, related records and deletions.
Control access to your data
Authenticate with an API key, limited to scopes like orders:read or orders:write.
Principle 01// REST API
Resources have plain names: orders, items, kits, contacts, projects and invoices, with JSON payloads and documented operations for each.
Automate the busywork.
Workflows react to orders, quotes and returns, then update records, create tasks or call your endpoint.
Start on an event, on a schedule or manually
Start a run when something happens in Filmo, on a schedule or by hand.
Run only when the conditions match
Add conditions and delays so each run only goes ahead when it should.
Connect the steps of each process
Chain steps that update records, create tasks or notify the team.
Send data to your endpoint
Send order data to your own endpoint with an HTTP request step.
Start with the context of each event
Start a run when an event happens in your workspace, with its details at hand.
Follow runs and retry failures
Follow each run step by step in the run log, and retry the one that failed.
Workflows, the REST API and MCP read and write one data model: the same orders, items and contacts.
Bring your AI assistant.
Connect an MCP client to your workspace and let it search, create and update records with the tools your key allows.
Delegate a sequence of tasks to an agent
Use your MCP client to coordinate multi-step work on orders, items and contacts.
Search and update records with tools
Search, create and update records through structured filmo_* tool calls.
Use several tools for one task
Let your client chain separate tool calls, from availability checks to tasks.
Choose what the assistant can access
Limit what an assistant can do with the key's scopes: orders:read or orders:write.
Connect Filmo to the client you use
Work from the MCP client you already use, next to your other servers.
Connect with an API key or OAuth. MCP tools follow the same scopes and limits as the REST API.
Principle 04// Docs
Each operation page shows the request in cURL, JavaScript and Python, and every response field by field.
List items
/api/v1/itemscurl https://app.filmo.io/api/v1/items \
--header "Authorization: Bearer $FILMO_API_KEY"fetch('https://app.filmo.io/api/v1/items', {
headers: {
Authorization: 'Bearer YOUR_FILMO_API_KEY'
}
})import requests
requests.get("https://app.filmo.io/api/v1/items",
headers={
"Authorization": "Bearer YOUR_FILMO_API_KEY"
}
)Response fields
200- data
- object[]
- pagination
- object
- meta
- object
Pick your surface.
Explore REST API, MCP and Workflows. The upcoming App SDK will help you build external applications connected to Filmo.