Doshka — online whiteboard for lessons, meetings and teamwork
Doshka API for developers
A REST API and webhooks to create boards and to read and change their contents from your own software: sticky notes with issues from a tracker and deals from a CRM, diagrams of shapes and arrows, editing and deleting elements, events about new notes and comments. Format: JSON; base URL: https://doshka-online.by/api/v1.
API key
- Sign in to Doshka and on the home page click API keys → Create key.
- The key (starts with dk_) is shown only once. Store it like a password.
- A key has the same rights as its owner: personal boards and the boards of the owner's organisations.
- Delete a leaked or unused key in the same place; requests with it stop working immediately.
Send every request with the header Authorization: Bearer followed by your key.
Methods
- GET /api/v1/me — the key owner: id, email, name.
- GET /api/v1/boards — boards: id, title, organisation, creation date.
- POST /api/v1/boards — create a board; the body may contain title and orgId.
- GET /api/v1/boards/ID — a board and its elements: type, position, size, text, sticky note colour.
- PATCH /api/v1/boards/ID — rename a board: title in the body.
- POST /api/v1/boards/ID/stickers — add sticky notes, up to 100 at once; without x and y they line up in rows below everything on the board.
- POST /api/v1/boards/ID/elements — draw shapes, text and arrows, up to 200 at once; see “Diagrams” below.
- PATCH /api/v1/boards/ID/elements/ID — change an element: text, color, x, y, width, height, link; send only what changes.
- DELETE /api/v1/boards/ID/elements/ID — delete an element together with its label; connected arrows stay but are detached.
- GET /api/v1/webhooks — your webhooks and their status.
- POST /api/v1/webhooks — subscribe to board events: boardId, the https://… address of your server and an events list; the response contains the secret for checking signatures (shown once).
- DELETE /api/v1/webhooks/ID — unsubscribe.
Sticky note: text, color and optional x, y. Colours: yellow, green, blue, pink, orange, violet, red, teal, lime, cyan, gray, white.
Limit: 120 requests per minute per key; above that the API answers 429.
Example: add a sticky note
curl, Python and JavaScript: the same request.
curl -X POST https://doshka-online.by/api/v1/boards/BOARD_ID/stickers \
-H "Authorization: Bearer dk_..." \
-H "Content-Type: application/json" \
-d '{"stickers":[{"text":"PROJ-12 Login page","color":"pink"}]}'import requests
requests.post(
"https://doshka-online.by/api/v1/boards/BOARD_ID/stickers",
headers={"Authorization": "Bearer dk_..."},
json={"stickers": [{"text": "PROJ-12 Login page", "color": "pink"}]},
)await fetch("https://doshka-online.by/api/v1/boards/BOARD_ID/stickers", {
method: "POST",
headers: { Authorization: "Bearer dk_...", "Content-Type": "application/json" },
body: JSON.stringify({ stickers: [{ text: "PROJ-12 Login page", color: "pink" }] }),
});
Diagrams: shapes and arrows
POST /api/v1/boards/ID/elements takes an elements list. type: sticker, rectangle, ellipse, diamond, text or arrow; text is the label of a shape or arrow, or the text itself; color uses the sticky note colours; x, y, width, height, link (https:// only). An arrow connects from and to: the id of an element on the board or the ref of a shape in the same request. Arrows stay attached: drag a shape and its arrows follow. If an arrow points to a missing element, the whole request is rejected and the board does not change. With layout (right or down), shapes without x and y are laid out automatically as a flowchart: in layers along the arrows, below the board content.
curl -X POST https://doshka-online.by/api/v1/boards/BOARD_ID/elements \
-H "Authorization: Bearer dk_..." \
-H "Content-Type: application/json" \
-d '{"layout":"right","elements":[
{"type":"rectangle","ref":"order","text":"Order","color":"blue"},
{"type":"diamond","ref":"paid","text":"Paid?"},
{"type":"ellipse","ref":"ship","text":"Ship","color":"green"},
{"type":"arrow","from":"order","to":"paid"},
{"type":"arrow","from":"paid","to":"ship","text":"yes"}
]}'PATCH moves a shape together with its label and the ends of its arrows. The API does not change an element locked on the board (response 409).
n8n nodes
The n8n-nodes-doshka package: the Doshka node creates and renames boards, adds sticky notes (input items are sent in batches of 100), draws diagrams with automatic layout, edits and deletes elements; the Doshka Trigger node starts a workflow when a sticky note is created, updated or deleted, a comment is added or the board changes. n8n creates and removes the webhook subscription by itself and checks the signature of every message. Doshka API credentials take your key. For the trigger, n8n must be reachable from the internet over https.
n8n → Settings → Community nodes → Install → n8n-nodes-doshka
MCP server for AI assistants
MCP (Model Context Protocol) is the standard AI assistants use to work with other services. With the Doshka MCP server you can ask your assistant “put the tasks from this email on a new board as sticky notes” or “draw a diagram of our order process”, and it does it and sends you the board link.
Setup: 1) create an API key (Doshka home page → API keys); 2) install Node.js 18 or newer; 3) download https://doshka-online.by/doshka-mcp.mjs: this one file is the whole server, no other packages; 4) add it to your assistant's settings as in the example below (Claude Desktop: Settings → Developer → Edit Config; Cursor: the .cursor/mcp.json file), with your key instead of dk_... and the path where you saved the file. Check: node doshka-mcp.mjs --check.
{
"mcpServers": {
"doshka": {
"command": "node",
"args": ["C:\\Users\\me\\Downloads\\doshka-mcp.mjs"],
"env": { "DOSHKA_API_KEY": "dk_..." }
}
}
}Or skip the download and use npm (package doshka-mcp); Node.js fetches it by itself:
{
"mcpServers": {
"doshka": {
"command": "npx",
"args": ["-y", "doshka-mcp"],
"env": { "DOSHKA_API_KEY": "dk_..." }
}
}
}Claude Code, in one command:
claude mcp add doshka -e DOSHKA_API_KEY=dk_... -- npx -y doshka-mcpTools: list_boards, create_board, get_board, rename_board, add_stickers, draw_diagram (shapes without coordinates are laid out automatically along the arrows), update_element, delete_element. The server runs on your computer and talks only to the Doshka API with your key: Doshka does not send board content to AI services; the assistant you chose does that when you ask.
Webhooks
- Events: board.changed is a summary: how many elements were added, edited and deleted, how many comments, and who made the changes; sticker.created, sticker.updated and sticker.deleted carry the notes themselves: id, text, colour, position, link; comment.added carries the comment text and the element it was left on. Without events only board.changed is sent.
- Changes within 5 seconds are grouped: one POST per event, up to 100 records in items, and the X-Doshka-Event header holds the event name. This makes triggers in n8n, Make and Zapier easy: “new sticky note → issue in the tracker”, “comment → chat message”.
- The X-Doshka-Signature header contains sha256= and the HMAC-SHA256 of the request body with the subscription secret. Check it before trusting the request.
- The address must be https on port 443, outside internal networks, without redirects; we wait 5 seconds for a response. After 20 failures in a row the subscription is switched off. Up to 20 webhooks per account.
{
"boardId": "BOARD_ID",
"url": "https://example.com/doshka-hook",
"events": ["sticker.created", "comment.added"]
}{
"event": "sticker.created",
"boardId": "…",
"title": "…",
"at": "2026-11-16T10:00:00.000Z",
"by": ["…"],
"items": [{ "id": "…", "text": "PROJ-12 Login page", "color": "pink", "x": 320, "y": 240 }]
}Checking the signature (Node.js):
import { createHmac, timingSafeEqual } from "node:crypto";
// rawBody — the raw request body (Buffer), secret — whsec_… from the subscription response
function isFromDoshka(rawBody, signature, secret) {
const expected = Buffer.from("sha256=" + createHmac("sha256", secret).update(rawBody).digest("hex"));
const got = Buffer.from(String(signature ?? ""));
return got.length === expected.length && timingSafeEqual(got, expected);
}
Embedding and oEmbed
The iframe code is under Share → Embed on a website. An embedded board is view-only and updates live.
oEmbed: GET /oembed?url= followed by a view-only board link. The response is type rich with the iframe code. Errors: 404 means it is not a board link, 401 means link access is off or the board has a password.
Machine-readable description
The API description in OpenAPI 3.1 format, ready to import into Postman, n8n, Make and client generators: https://doshka-online.by/openapi.json
Errors
A response with a non-2xx code contains an error field with the error text; element edits also return code (missing, locked, geometry, color, link, text). 400: invalid request body; 401: missing or invalid key; 404: the board or element does not exist or you have no access; 409: the element is locked; 429: too many requests.
Help · Guides · Questions and answers · Moving from Miro · Moving from Holst · Doshka and other online whiteboards: an honest comparison · Supported languages · Doshka integrations · Doshka API for developers · About · Terms of Use · Privacy Policy · Contacts · Licenses · Templates · Use cases · Articles
Other languages: Русский · Беларуская · Қазақша · Oʻzbekcha · Кыргызча · Тоҷикӣ · Հայերեն · Azərbaycanca · Română · Türkmençe · Latviešu · Lietuvių · Polski · Eesti