Table of contents

The Fugo API is a REST API that lets developers manage a Fugo account programmatically - creating content, uploading media, publishing playlists, and reading back screen and space information - from their own applications, scripts, or internal tools, without going through the Fugo CMS interface.

It's built for teams who want to connect Fugo to their own systems: pulling screen inventory into an internal dashboard, auto-generating content from another platform, or wiring Fugo into a broader automation pipeline you're building yourself.

Before you can call the API, you'll need to generate an API key. Every request to the API is authenticated with one.

From the Fugo CMS, open Settings from your account menu, then go to the Team section and select the API keys tab.

Each API key you've created is listed as its own card showing:

If you haven't created any keys yet, you'll see "No API keys yet" in place of the list.

Click Create API key, give it a name that describes what it's for (for example, "production API" or the name of the internal tool that will use it), then click Create key.

Use the pencil icon on a key's card to rename it in place, or the trash icon to delete it.

Deleting a key is immediate and can't be undone - any application still using that key will stop being able to access your account as soon as it's deleted, so make sure nothing is still relying on a key before you remove it.

There's currently no way to temporarily disable a key or set it to expire automatically - deleting and recreating a key is the only reset option. Each key also applies to your whole account rather than a limited set of permissions, so treat every key with the same care you'd give a password: anyone who has it can create, edit, or delete your content.

Every request to the Fugo API needs your API key attached as a header:

Requests missing the x-api-key header, or using a key that's been deleted or mistyped, will be rejected.

The current API surface covers the core building blocks of getting content onto screens: content, media, playlists, screens, and basic tenant/space information. It doesn't yet cover every area of the CMS - user and role management, for example, isn't available through the API today and can only be managed from the CMS itself.

Create content items, update them, and retrieve their details - including the editable text fields inside a piece of content, so you can update copy programmatically without opening the Design Studio.

Upload media into your Fugo library several ways - from a remote URL, as base64-encoded data, as a raw binary upload, or via a multipart upload - and update or delete existing media afterward. Uploading a new version of an existing media item is a convenient way to refresh content that's already live: any playlist using that media picks up the new version automatically, the same as if you'd updated it from inside the CMS.

To list your media library, a paginated endpoint returns items in batches using a cursor rather than page numbers, with each page capped at 1MB of response data - useful to know if you're syncing a large library and need to page through results rather than pulling everything in one call.

Deleting a media item is non-destructive: rather than erasing the file, it's moved to a deleted-items table and any URL mappings pointing to it are removed, so a delete can be recovered from on the Fugo side if needed.

Create playlists, list your existing manual playlists, and list every playlist in a Space. A new playlist is targeted at specific screens or screen groups (by player ID or player group ID, rather than by name or a property like region), and can include a start and end date plus a recurring weekly schedule - for example, running only on certain days of the week within specific time windows.

You can also fire manual triggers by name or ID through the same playlists surface.

Retrieve every screen registered to a Space - useful for pulling your current screen inventory into an internal tool or dashboard rather than checking the CMS by hand.

Screens are read-only through the API today; creating, renaming, or removing a screen still needs to happen from the CMS.

Look up your account's tenant details and list every Space in your workspace.

The API is currently versioned as v1, reflected in every endpoint path under the base URL https://api.fugo.ai/rest/v1 (for example, the media endpoints live under /v1/medias). There's no separate v2 surface today.

There's no published rate limit for API requests as of this writing. If you're planning high-volume or bursty usage (for example, syncing thousands of media items on a schedule), reach out to support first so we can advise on the best approach.

The full endpoint reference - every operation with its parameters, headers, and example requests and responses - is published at docs.fugo.ai. Use it alongside this article when you're building against the API.

If you're connecting Fugo to Zapier, that integration authenticates separately from the API keys described in this article - you won't need to create or manage an API key for it.

And if what you actually want is to control your Fugo account using natural-language requests to an AI assistant - rather than writing code against the API directly - that's a different, purpose-built connector. See the Fugo MCP Overview article for that.

Have a question that isn't covered here? Reach out via the support chat inside the Fugo CMS, or email us at support@fugo.ai.

Don't have a Fugo account yet? Start a free trial.