OpenAI Custom GPT with footage.one

Overview

OpenAI Custom GPTs currently do not support MCP, but do support OpenAPI Actions with OAuth2. You therefore interact with the footage.one API via REST + OAuth2.

Steps

1. Get the OpenAPI spec

Official Swagger UI: https://app.footage.one/api/asset/swagger-ui.html

Note: the machine-readable spec at /v2/api-docs currently requires auth — export the JSON spec from the UI or fetch it with a valid token. A public spec is in progress.

2. Configure the Action

In the GPT Builder under Configure → Actions → Create new action:

• Authentication: OAuth
• Client ID / Client Secret: from your OAuth2 client in Keycloak (see OAuth2 for third-party apps)
• Authorization URL: Keycloak auth endpoint
• Token URL: Keycloak token endpoint
• Scope: openid profile email
• Schema: paste the OpenAPI JSON

3. Test prompt

Search for assets with the keyword "sunset" and give me the first three with description and download link.

The GPT runs the OAuth flow (once), calls search/assets and follows the _links to the detail and download URL.

Tips

• Action descriptions: keep the summary fields in the OpenAPI spec well-maintained — the GPT uses them to decide which Action to call.
• Response size: limit limit to 5–10 so the context does not overflow.
• Privacy: Custom GPTs send Action calls via OpenAI servers. Check whether this is compatible with your GDPR agreement.

Next steps

• REST API Quickstart
• OAuth2 for third-party apps