Three ways to connect a system to your screens
Write code, talk to an assistant, or send an email. Each one reaches the same screens.
REST API with API keys
Manage a Fugo account from your own applications, scripts or internal tools. Create content, upload media, publish playlists and read back your screens and Spaces. Every request is authenticated with an API key you create in Settings. Read the docs for the full list of endpoints.
- Base URL api.fugo.ai/rest/v1, version 1
- x-api-key header on every request
- Content, media, playlists, screens, tenant and Spaces
- API keys are included on the Enterprise plan
MCP server for AI assistants
Fugo runs an MCP server, so an AI assistant can work with your account in plain language. Ask it what is playing on a screen, upload media, publish a playlist or fire a trigger. It acts with your own Fugo role, and most assistants ask you to confirm before they change anything.
- Claude, ChatGPT and Microsoft 365 Copilot
- Screens, media, playlists, triggers, layouts and Spaces
- Any MCP client can connect at api.fugo.ai/mcp
Email triggers, with no integration
If a system can send an email, it can put content on a screen. Each email trigger has its own address. Point a notification at it and matching emails play on the screens you choose. There is nothing to build and no API key to manage.
- A unique address for each trigger
- Works with any system that sends email
- No sign-in or connection step
What you can do with the API
Everything here works with an API key today. Read the docs for every endpoint.
Content
Create and update content from the systems that already hold the data.
Media
Upload and manage media. Upload a new version and every playlist using it picks up the change.
Playlists
Create playlists with a start and end date and a weekly schedule.
Manual triggers
Fire manual triggers by name or ID from your own pipeline.
Screens
Read every screen in a Space. Setup and renaming stay in Fugo.
Spaces and tenant
Read your Spaces and tenant details to map your estate.
What teams build on the Fugo API
From internal dashboards to full automation pipelines.
Screen inventory in your own tools
Pull every screen in a Space into an internal dashboard, so your IT team sees the estate without opening the CMS. Screens are read-only through the API, so setup and renaming stay in Fugo.
Access you control
A Workspace Admin creates API keys in Settings. A key applies to your whole account, so treat it like a password.
- x-api-key header on every request
- Keys created by a Workspace Admin
- MCP acts with your own Fugo role
- Assistants confirm before changing anything
- SOC 2 Type II, HIPAA and GDPR