MURAL Public API

Name: MURAL Public API API
Brand: MURAL Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationoauth288 EndpointsREST

For Agents

Create and populate MURAL boards, add sticky notes and other widgets, export images, and manage workspace rooms and templates programmatically.

Connect the MURAL Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MURAL Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MURAL Public API API.

Create, duplicate, update, and delete murals via /murals and /murals/{muralId}

Author sticky notes and other widgets through the mural contents endpoints

Generate image and PDF exports via POST /murals/{muralId}/export and poll GET /murals/{muralId}/exports/{exportId}

Manage rooms that group murals within a workspace via the rooms endpoints

GET STARTED

Start building with MURAL Public API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MURAL Public API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MURAL Public API, keeping it validated and agent-ready. MURAL's Public API exposes the visual collaboration platform's workspaces, rooms, murals, templates, and mural-content widgets so teams can automate board creation, populate sticky notes from upstream tools, export images, and manage workspace membership at scale. Across 88 endpoints it covers full lifecycle management of murals — creation, content authoring, duplication, export, private mode, plus the surrounding rooms, templates, users, and search resources.

Use Cases

Patterns agents use MURAL Public API API for, with concrete tasks.

★ Auto-Generate Workshop Boards from a Template

Facilitators preparing a workshop duplicate a templated mural per breakout group instead of hand-creating boards. POST /murals duplicate or POST /murals/{muralId}/duplicate creates the new boards in the right room, and bulk content endpoints seed each board with the agenda widgets. A 10-team workshop turns from 30 minutes of clicking into one API run.

Call POST /murals/{muralId}/duplicate ten times in the chosen room, each renamed for the breakout team, and seed the agenda widgets via the mural contents endpoints.

Sync Sticky Notes from Survey or Ticket Data

Insights teams pull customer feedback from a survey tool or support ticket queue and auto-populate a MURAL board with one sticky note per response. The mural contents endpoints accept widget payloads with text, color, and position, so a clustering exercise can begin with the data already laid out by theme. This collapses the prep step that usually precedes affinity mapping sessions.

For each survey response, call the mural contents widget creation endpoint with the response text and a position computed from a grid layout.

Mural Export for Meeting Recaps

Project managers send a flat image of the post-meeting mural to attendees who could not attend live. POST /murals/{muralId}/export kicks off the render and GET /murals/{muralId}/exports/{exportId} returns the asset when ready. The flow runs unattended and the image attaches to a recap email or doc without anyone re-opening MURAL.

Call POST /murals/{muralId}/export with format = png, poll GET /murals/{muralId}/exports/{exportId} until the asset is ready, then attach it to the recap email.

Agent-Driven Workshop Setup in Chat

An AI assistant in a team chat creates and pre-populates a MURAL board when a user asks 'set up a retro for tomorrow'. Through Jentic the agent searches for 'create a mural and add sticky notes', loads the schema, calls POST /murals to create the board, and posts the link back in chat with seeded sticky notes ready for the team. OAuth2 credentials stay in the Jentic vault.

Search Jentic for 'create a mural', execute POST /murals with the chosen room id, then chain widget creation calls to seed the retro columns.

Key Endpoints

88 endpoints — jentic publishes the only available openapi specification for mural public api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/murals

Create a new mural

GET

/murals/{muralId}

Retrieve a mural by id

POST

/murals/{muralId}/duplicate

Duplicate an existing mural

POST

/murals/{muralId}/export

Trigger an image or PDF export

GET

/murals/{muralId}/exports/{exportId}

Poll export status

POST

/murals/{muralId}/private-mode/start

Start private mode for a facilitated session

POST

/murals

Create a new mural

GET

/murals/{muralId}

Retrieve a mural by id

POST

/murals/{muralId}/duplicate

Duplicate an existing mural

POST

/murals/{muralId}/export

Trigger an image or PDF export

GET

/murals/{muralId}/exports/{exportId}

Poll export status

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MURAL OAuth 2.0 grants are held in the encrypted Jentic vault, refreshed automatically, and the agent only ever receives a scoped session token. The raw access and refresh tokens never enter prompt context or logs.

Intent-based discovery

Agents search Jentic with intents like 'create a mural' or 'add a sticky note to a mural' and Jentic returns the matching MURAL operation with its input schema, hiding the widget-payload conventions and the workspace-room-mural hierarchy.

Time to first call

Direct MURAL integration: 3-5 days for OAuth flow, refresh handling, and widget payload structure. Through Jentic: under 1 hour to create a first mural and seed it with sticky notes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Miro REST API

Miro is the leading alternative visual collaboration platform with a comparable board and widget API

Pick Miro when the team standardises on Miro boards or when an existing Miro workspace and OAuth grant are already in place.

Alternative

Figma REST API

Figma covers structured design canvases — alternative when the workflow is design rather than facilitation

Choose Figma when the canvas is for design files and components rather than facilitated workshops or stickies.

Complementary

Slack Web API

Slack is where created mural links and exports are most often shared back to the team

Pair with MURAL when the post-creation step is announcing the new mural in a Slack channel.

FAQs

Specific to using MURAL Public API API through Jentic.

Why is there no official OpenAPI spec for MURAL Public API?

MURAL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MURAL Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MURAL Public API use?

The MURAL Public API uses OAuth 2.0 with user-delegated access tokens. Through Jentic the OAuth grant is held in the encrypted vault and refreshed automatically, so the agent never handles the raw access or refresh token.

Can I add sticky notes to a mural programmatically?

Yes. The mural contents endpoints accept widget creation payloads — including sticky notes with text, color, and x/y position — so a script or agent can populate a board with structured input rather than manual drag-and-drop.

What are the rate limits for the MURAL Public API?

MURAL applies per-app and per-user rate limits and surfaces remaining quota in response headers. Heavy widget-creation workflows should batch within a single mural and back off when 429 responses are returned to avoid temporary blocks.

How do I export a mural to PNG through Jentic?

Search Jentic for 'export a mural to image', execute POST /murals/{muralId}/export with format = png, then poll GET /murals/{muralId}/exports/{exportId} until the asset is ready. The agent receives the asset URL without ever touching the raw OAuth token.

Is the MURAL Public API free?

API access is included with paid MURAL workspace plans. Some features such as private mode and certain export formats require higher tiers — check the workspace's plan limits before scripting heavy use.

Can I duplicate a template mural for each breakout team?

Yes. POST /murals/{muralId}/duplicate creates a copy of an existing mural — typically a template — into a chosen room. Loop the call once per team to spin up parallel boards in seconds.