Workspaces

Get Writing Style

What the email writer learned from this workspace's own decisions on AI drafts (RO-282): approvals, edits (with their diffs), rejections with reasons and Ask Zero's thumbs. The rules, the short versioned block the writer prompt gets, and the decisions counted. No model training; nothing is shared across workspaces.

API key access

Needs the leads:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
GET/api/v1/workspaces/current/writing-style
AuthorizationBearer <token>

Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).

In: header

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Response Body

curl -X GET "http://localhost:8000/api/v1/workspaces/current/writing-style" \  -H "X-Workspace-Id: string"
{
  "enabled": true,
  "format": "string",
  "version": 0,
  "block": "string",
  "rules": [
    {
      "code": "string",
      "text": "string",
      "evidence": 0
    }
  ],
  "samples": 0,
  "learned_at": "2019-08-24T14:15:22Z",
  "decisions": {
    "approved": 0,
    "edited": 0,
    "rejected": 0,
    "thumbs_up": 0,
    "thumbs_down": 0
  },
  "can_manage": true
}