Dashly Docs

Introduction

What you can build on Dashly, and where each surface lives.

Dashly is an all-in-one workspace for marketing agencies: CRM, deals, projects, tickets, time tracking, a client portal and reporting. Everything the dashboard does is also open to code and to AI assistants, through four surfaces.

What you can build

REST API. A JSON API over every collection of the product: clients, contacts, deals, leads, projects, tickets, comments, time logs, documents and more. The API is generated from a single resource catalog, so every resource behaves the same way: the same pagination, the same filter and sort grammar, the same error envelope, the same scopes. Learn one resource and you know them all. Beyond create, read, update and delete, the product's gestures (converting a lead, merging two deals, importing a CSV) are exposed as actions.

MCP server for AI assistants. A Model Context Protocol server that lets Claude, ChatGPT, Cursor or any MCP client work inside an agency's workspace. It sits on top of the REST API: same permissions, same limits, same audit trail. Members connect with one click through OAuth; integrations can use an API key.

Client-portal MCP. A second MCP server for an agency's clients: their own assistant can list their projects and requests, open a new request or reply on one, in their client space only.

Outbound webhooks. Dashly can POST a signed JSON event to your endpoint when something happens, for example when a ticket or a client is created.

Base URLs

SurfaceURL
REST APIhttps://api.usedashly.com/v1
MCP server (agency)https://mcp.usedashly.com
MCP server (client portal)https://mcp.usedashly.com/portal
OAuth authorization serverhttps://app.usedashly.com
Dashboardhttps://app.usedashly.com

Records are always addressed by their public id, a short string such as hsbftmp3f5, in paths and in links between records alike.

Start here

On this page