Developer resources

All interfaces, specs and guides on one page. API and MCP are available in all plans, including the free tier.

One URL is all you need to get started

The entire API is discoverable via HATEOAS links from a single URL. You can start right away — no spec file needed.

curl https://app.footage.one/api/asset/

Response contains _links to all resources and a documentation link to the Swagger UI.

API reference

Machine-readable and interactive API documentation.

Interactive REST API documentation with Try-It-Out.

API Root (HATEOAS)

Entry point — all endpoints discoverable via _links.

Machine-readable directory of all footage.one APIs.

REST API Quickstart

curl examples, auth, pagination — get started right away.

MCP Server

Model Context Protocol for Claude Desktop, n8n and LangChain — endpoint, auth and tool list in the docs.

MCP endpoint docs

https://mcp.footage.one/mcp — Streamable HTTP. Setup steps and auth details.

Machine-readable description of the MCP server.

AI-oriented overview of the platform.

Auth

Personal API token for REST or OAuth2 with PKCE for third-party apps.

Account / API Token

Generate a personal API token in the Asset Manager.

API tokens — docs

Create, use and scope tokens for public endpoints.

OAuth2 for third-party apps

PKCE flow for multi-user apps and Custom GPTs.

Machine-readable endpoint list from Keycloak (realm footageone).

Integrations

Setup guides for Claude Desktop, n8n, LangChain, Custom GPTs, Zapier and Make.

Connect the MCP server to Claude Desktop.

MCP Client Tool node for workflow automation.

LangChain & LangGraph

Python and JavaScript SDK snippets.

OpenAI Custom GPT

OpenAPI Actions with OAuth2.

Zapier / Make.com

No-code automation via REST.

Agentic Cookbook

Five proven prompt patterns for common tasks.

Standards

footage.one is built on open standards throughout.

OpenAPI / Swagger

API spec in standardised format.

MCP — Model Context Protocol

Spec at modelcontextprotocol.io.

HATEOAS / HAL+JSON

Hypermedia-driven REST — discovery via _links.

Authorization Code Flow with PKCE.

Architecture note

The main API for integrations is /api/asset/ (REST with HATEOAS). There is also an internal GraphQL service for the search component (apps/ork) — this is not intended for external integration. Always use the asset API for agents and third-party apps.

[email protected]