Skip to main content

June 2026

Insights Submission API, workspace API tokens, and the CreateStoryMap MCP tool.

Written by Arpad Tamas

June 21

Insights Submission API

You can now send insights into StoriesOnBoard straight from your own systems — your product, your support tool, or a data pipeline — through a new server-side API. Until now feedback could only arrive via the public idea portal, Zapier, the Chrome extension, or in-app; there was no documented backend API for it.

A POST /api/v1/insights/submissions call creates an insight in the feedback inbox of the product your token targets:

  • Send content (the insight text) and an optional sourceEmail. A successful call returns 201 Created with a feedbackId and a correlation id for support lookups.

  • Submitted insights behave like any other feedback: they land in the right product inbox, trigger your feedback automations, and are written to the audit/activity log. They're tagged with an Api source, so you can tell them apart from Zapier, portal, in-app, or Chrome submissions — and use that as its own automation condition.

  • Server-side only: the token is a Bearer credential in the Authorization header. No browser CORS, client-side JavaScript, query-string, or cookie tokens. Rate limiting and safe JSON errors are built in, and errors never leak the token secret.

Workspace API tokens

The new API uses a new kind of credential — a workspace API token — managed under Workspace settings → API tokens.

  • WorkspaceAdmins can create and revoke tokens (no SubscriptionAdmin role required); they see only the API tokens tab.

  • When creating a token you pick the target product the token's insights go to, and optionally an expiry (UTC).

  • The full token value (sob_wat_…) is shown only once, at creation. After that the list shows just the safe token id, which is enough for support lookups, audit review, and revocation — but not for API calls.

  • The list shows each token's name, safe id, target product, creator, created/expiry dates, status, and last used time. Tokens can be revoked at any time and immediately stop authenticating.

June 14

Create story maps with your AI agent

AI agents can now build a story map from scratch. Previously all MCP tools worked on a story map that already existed, so any "requirements → story map" agent flow had a manual step: leave the agent, open StoriesOnBoard, run the create wizard, and copy the new map's id back. The new CreateStoryMap tool removes that step — starting from a PRD or a conversation, the agent can now stand up the whole map on its own. It's our 15th MCP tool.

  • Creates an empty map in your workspace with the usual defaults (4 statuses, 7 annotations, default theme/colors, story points as the estimation unit, WorkspaceVisible). You give a name, an optional description, and an optional product.

  • The response is immediately usable — id, slug, name, and board url — so the agent can keep going with GetStoryMapData, CreateStoryMapCard, etc., with no discovery round-trip. The new map also shows up in ListStoryMaps right away.

Start using StoriesOnBoard from your AI agent (sign up mid-flow)

If you meet StoriesOnBoard for the first time through an AI agent's connector, you can now create your account in the middle of the connector flow and land right back where you left off. After signing up, the browser returns to the same OAuth consent page — same client, scopes, and parameters — and your freshly created workspace is shown and pre-selected. Approve, and the agent finishes connecting in one go. (All the usual signup protections — reCAPTCHA, honeypot — still apply.)

Did this answer your question?