DailyDashboard API

Connect your own scripts and automation tools (Zapier, Make, Google Apps Script) to your DailyDashboard account. Read your clients, meetings, transcripts, tasks and invoices, and create and update tasks, follow-ups, meetings and goals, with a personal API key.

Overview

  • Base URL: https://dailydashboard.ai/api/v1
  • Every operation is a tool: GET /tools lists them and POST /tools/<name> runs one with its arguments as the JSON body. The API offers the same 31 tools as the Claude connector.
  • Requests and responses are JSON. Successful calls return 200 { "result": ... }.
  • For your own account. A key works only with the DailyDashboard account that created it and can never reach anyone else's data. It is for automating your own work, not for building apps for other people; to connect an app that other users sign in to, use the Claude connector (MCP with OAuth), where each person approves access themselves.
  • Requires a DailyDashboard account on a paid plan with an active subscription (or a running trial) and AI agents enabled.

Authentication

Create a key in DailyDashboard under Settings → Integrations → DailyDashboard API keys. Give each automation its own named key with only the permissions it needs. A key is shown once, when it is created; disable or delete it there at any time.

Send the key in the x-api-key header (or Authorization: ApiKey <key>):

curl https://dailydashboard.ai/api/v1/me -H "x-api-key: ddapi_..."

Permissions

read
Read clients, meetings, transcripts, tasks, invoices and activity, and look up clients by email.

write
Create and update tasks, follow-ups, meetings, goals and client profiles, and add files to a client's knowledge base.

Each tool below shows the permission it needs. Keys are never shown again and are stored only as hashes; keep them out of source control and don't share them: anyone holding a key acts as you.

Quick start

1. Check your key
curl https://dailydashboard.ai/api/v1/me \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY"
2. List what the key can do
curl https://dailydashboard.ai/api/v1/tools \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY"
3. Read a client’s open tasks
curl -X POST https://dailydashboard.ai/api/v1/tools/queryClientData \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId": "Acme Corp", "dataType": "tasks"}'
4. Add a task (preview first, then confirm)
curl -X POST https://dailydashboard.ai/api/v1/tools/createClientItem \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId": "Acme Corp", "itemType": "task", "details": {"description": "Send the SOW"}, "confirmation": true}'

Writes preview first

Tools that create or change data return a preview and write nothing until you call them again with "confirmation": true. Send the same arguments plus confirmation to make the change. The API never deletes clients or records, sends email or moves money.

Errors and limits

Errors return { "error": "<code>", "message": "..." }. The message is safe to show to a person.

  • 401
    api_key_required, Invalid API key, API key is disabled

    No key, an unknown key, or a disabled key.

  • 403
    subscription_required, plan_required

    The account needs a paid plan with an active subscription.

  • 403
    insufficient_permission

    The key lacks the tool’s permission (read or write). Change it in Settings.

  • 403
    agents_feature_disabled

    AI agents are not enabled for the account.

  • 404
    unknown_tool

    No tool by that name.

  • 422
    tool_error

    The tool refused the arguments; message says why and result holds its reply.

  • 429
    rate_limited

    Too many requests. Wait and retry.

  • 500
    tool_failed, internal_error

    Something went wrong on our side. Retry later.

Rate limit: 120 requests per minute per account. Responses carry RateLimit-* headers.

Endpoints

GET /api/v1/me

The account and key: { "user": { "uid", "email", "name" }, "apiKey": { "id", "permissions" } }.

GET /api/v1/tools

The tools this key can call, each with name, title, description, permission and its JSON Schema in inputSchema.

POST /api/v1/tools/<name>

Runs a tool. The body is its arguments; the reply is { "result": ... }.

Workflow endpoints

Two endpoints for email and file automations, with the same keys:

POST /api/integrations/client-mapping/lookup
read

Find which client a list of email addresses belongs to. Body: { "emails": ["sender@example.com"] }.

POST /api/integrations/client/knowledgebase
write

Add a JSON payload or a file (multipart, up to 25MB) to the matched client’s knowledge base. Body: emails plus payload or file, optional externalId (idempotent) and folder.

Tools

Read

Create and update

List Clients

read

POST /api/v1/tools/listClients

List the clients in this DailyDashboard account. Returns each client's id, name, kind ("client" for a paying client that is invoiced, "project" for the user's own personal project, which is tracked but not invoiced), domains and a short summary, plus the total count.

Parameters
  • querystring

    Optional case-insensitive filter matched against client names and domains.

  • kindstring

    Optional filter: "client" returns only paying clients, "project" only personal projects.

    • client
    • project
Example
curl -X POST https://dailydashboard.ai/api/v1/tools/listClients \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Query Client Data

read

POST /api/v1/tools/queryClientData

Read one category of client data (tasks, follow-ups, meetings, decisions, initiatives, OKR objectives, team, billing, contract terms and equity, time entries, recommendations, profile fields and more) for a single client, or aggregated across all of the user's clients when clientId is omitted. Returns the records for the requested dataType; each dataType value lists the shape it returns.

Parameters
  • dataTypestring
    required

    The type of data to retrieve

    • billing — Returns: { businessName, address, phone, email, rate, retainer, retainerHours, subscriptionStatus }
    • contract — Returns: { kind, nonCash, contractStartDate, contractEndDate, contractValue, rate, retainer, retainerHours, retainerRolloverPolicy, notToExceed, notToExceedHours, contractUrl, invoicingSchedule, invoicingInstructions, equity, equityExecutionDate, equityVestingPeriod } (the Contract section; equity is free text such as a percentage or share count)
    • team — Returns: { active: [...], departed: [...], total }
    • tasks — Returns: [{ id, text, priority, dueDate, createdAt, completed }] (open tasks; with includeCompleted, also recently completed ones)
    • meetings — Returns: [{ id, title, startTime, attendees, calendarSummary, aiSummary, transcript: { linked, source, documentUrl, status, processed, processingError } }] (aiSummary is empty until a linked transcript has been processed)
    • decisions — Returns: [{ id, text, createdAt, resolved }] (includes both resolved and unresolved decisions)
    • initiatives — Returns: [{ id, text, priority, status, createdAt }]
    • followups — Returns: [{ id, text, dueDate, assignedTeamMemberIds, createdAt, completed }] (open follow-ups; with includeCompleted, also recently completed ones)
    • referrals — Returns: [{ id, referralName, organization, email, clientId, clientName, referredBy, introductions, firstIntroducedAt, lastIntroducedAt, tags }]
    • timeEntries — Returns: [{ id, date, timeSpent, description, clientRate, calculatedAmount }]
    • dictionary — Returns: [{ id, term, definition, category, createdAt }]
    • techStack — Returns: { fields: { [field]: { label, value, url? } }, customItems: [{ label, value, url? }] } (the Tech Stack section)
    • budget — Returns: { totals: { totalBudget?, spentBudget?, remainingBudget? }, items: [{ name, amount, type }] } (the Budget section)
    • sprint — Returns: { startDate, length, planningDay, reviewDay, velocity, currentSprint }
    • templates — Returns: [{ templateId, templateName, templateType, assignedAt, resourceUrl }] (only the templates assigned to this client)
    • impact — Returns: { clientImpact: [{ text, url? }], personalImpact: [{ text, url? }] } (the Impact section)
    • customLinks — Returns: [{ label, url }]
    • recommendations — Returns: [{ id, eventId, eventTitle, eventDate, recommendedTasks, recommendedInitiatives, recommendedDecisions, recommendedFollowUps, recommendedObjectives, status }]
    • mission — Returns: client mission statement
    • vision — Returns: client vision statement
    • goals — Returns: { goals, goalsUrl } (the client's free-text goals statement; tracked OKRs are under objectives)
    • objectives — Returns: { data: [{ id, title, description, owner, period, periodLabel, status, confidence, score, keyResults: [{ id, title, startValue, targetValue, currentValue, unit, progress }], carriedForwardFrom, carriedForwardTo }] } (OKR objectives from the Goals section: active ones, latest period first; with includeCompleted, also recently graded ones)
    • domains — Returns: client domain information
    • terminology — Returns: client-specific terminology
    • urls — Returns: { website, staging, production, ... }
    • integrations — Returns: Drive, templates, and other integration config
    • github — Returns: { repos: [{ fullName, provider, role, htmlUrl, includeInTimesheets, sync }], lastSyncedAt } (linked GitHub, GitLab, Azure Repos and Bitbucket repositories)
    • issueTracker — Returns: { projects: [{ provider, key, name, kind, url, sync }], lastSyncedAt } (linked Jira projects, Linear teams, monday.com boards, ClickUp spaces or folders and Azure DevOps projects)
    • chat — Returns: { channels: [{ provider, name, workspace, url, sync }], lastSyncedAt } (linked Slack and Microsoft Teams channels)
    • setup — Returns: client onboarding and setup data
    • summary — Returns: client summary overview
    • all — Returns every category for the client (single-client only)
  • clientIdstring

    The client's ID or name. Omitted: the query covers all clients and returns a cross-client rollup.

  • includeCompletedboolean

    tasks / followups / objectives only: also return the most recently completed (or, for objectives, graded) items. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/queryClientData \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"dataType":"billing"}'

Search Client Knowledge Base

read

POST /api/v1/tools/searchClientKnowledge

Semantic search over a client's knowledge base: historical meeting transcripts, documents and notes. Returns the matching passages (vectorResults) plus current tasks, decisions, initiatives and follow-ups for the client (realTimeContext).

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • querystring
    required

    Search query for the vector store

  • limitnumber

    Maximum number of vector store contexts to return

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/searchClientKnowledge \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","query":"<query>"}'

Get Portfolio Team Members

read

POST /api/v1/tools/getPortfolioTeamMembers

List client team members across the user's whole portfolio, filtered by role, person name, email, keyword, client or status. Returns the matching members, total and returned counts, and a count per role.

Parameters
  • rolestring

    Role keyword to filter (e.g., CEO, COO, CTO)

  • rolesarray of strings
  • clientIdstring

    Filter to a single client ID or name

  • clientNamestring

    Fuzzy match on client name

  • namestring

    Filter by person name

  • searchstring

    Keyword search across name, role, and tags

  • emailstring

    Filter by email address

  • includeDepartedboolean

    Include archived/departed members

  • statusesarray of strings

    Array of statuses to include

  • limitnumber

    Maximum members to return (default 25, max 200)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getPortfolioTeamMembers \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Portfolio Rollup

read

POST /api/v1/tools/getPortfolioRollup

Aggregate metrics across all of the user's clients for one kind: financials, retainers, tasks, follow-ups, meetings, recommendations, clients, referrals or decisions, optionally filtered by client, amount or date. Returns the aggregated totals and matching records for that kind. Financials and retainers cover paying clients only; personal projects (kind "project") are not invoiced.

Parameters
  • kindstring
    required
    • financials
    • retainers
    • tasks
    • followups
    • follow-ups
    • meetings
    • recommendations
    • clients
    • referrals
    • decisions
  • filtersobject
    • clientIdstring

      Client ID or name

    • clientNamestring
    • minAmountnumber
    • maxAmountnumber
    • datestring
    • limitnumber
Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getPortfolioRollup \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"kind":"financials"}'

Get GitHub Activity

read

POST /api/v1/tools/getGithubActivity

Read recent activity from the GitHub, GitLab, Azure Repos and Bitbucket repositories linked to a client: pull requests (GitLab merge requests count as pull requests), issues, releases, milestones and the user's own commits, newest first, with counts of merged PRs, closed issues, open PRs and releases. Data comes from DailyDashboard's repository sync (every 2 hours or on demand), not the live code host. Returns a message when the client has no linked repositories.

Parameters
  • clientIdstring
    required

    Client ID (or client name) whose linked repositories to read.

  • typesarray of strings

    Activity types to include (default: pr, issue, release).

    • pr
    • issue
    • release
    • milestone
    • commit
  • statestring

    Filter by state (default all). 'merged' applies to pull requests; 'closed' includes merged pull requests.

    • all
    • open
    • closed
    • merged
  • sincestring

    ISO date or datetime; only items updated on or after it (default: 14 days ago).

  • untilstring

    ISO date or datetime; only items updated on or before it (default: now).

  • repostring

    Optional repository filter (owner/name or part of it).

  • limitnumber

    Maximum items to return (default 50, max 200).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getGithubActivity \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>"}'

Get Chat Activity

read

POST /api/v1/tools/getChatActivity

Read recent messages from the Slack and Microsoft Teams channels linked to a client (per channel, newest first) and the pending @-mentions of the user that may be action items. Filter by channel and date window. Data comes from DailyDashboard's chat sync (every 2 hours or on demand), not the live workspace. Returns a message when the client has no linked channels.

Parameters
  • clientIdstring
    required

    Client ID (or client name) whose linked channels to read.

  • providerstring

    Optional: only channels of this provider.

    • slack
    • teams
  • channelstring

    Optional channel filter (part of the channel name).

  • sincestring

    ISO date; only messages on or after it (default: 7 days ago, at most 90 days back).

  • untilstring

    ISO date; only messages on or before it (default: today).

  • limitnumber

    Maximum messages to return per channel (default 20, max 100).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getChatActivity \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>"}'

List Templates

read

POST /api/v1/tools/listTemplates

List the user's whole template library, assigned to a client or not, optionally searched by name, description or category (matching templates contain every query word) or filtered by category or type. Returns each template's id, name, type (drive: a Google Drive file copied into a client's folder when assigned; link: any URL), format, category, description, url and assignedClients ([{ clientId, clientName, copyUrl }]), plus total and matched counts and the list of categories.

Parameters
  • querystring

    Optional search words matched (case-insensitively, every word) against template names, descriptions and categories, e.g. "due diligence interview".

  • categorystring

    Optional: only templates in this category (exact name, case-insensitive).

  • typestring

    Optional: only Google Drive templates (drive) or link templates (link).

    • drive
    • link
  • limitnumber

    Maximum templates to return (default 50, max 200).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/listTemplates \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Read Template

read

POST /api/v1/tools/getTemplateContent

Read one template from the user's template library, by templateId or name: its details and the text of its Google Doc (or Word, PDF or text file), one page at a time. Returns the template fields with text, characters, offset, returnedCharacters, hasMore and nextOffset. Spreadsheets, slides, forms and links outside Google Drive return their details and url with a message and no text; several name matches return candidates.

Parameters
  • templateIdstring

    The template's id (the id field of a template record).

  • namestring

    The template's name, used when templateId is not given. When several templates match, they are returned as candidates.

  • offsetnumber

    Character offset to start reading from (default 0). Each page reports nextOffset for the following page.

  • maxCharactersnumber

    Maximum number of characters in this page (default 24000, max 150000).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getTemplateContent \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Issue Tracker Issues

read

POST /api/v1/tools/getIssueTrackerActivity

Read issues from the Jira projects, Linear teams, monday.com boards, ClickUp spaces or folders and Azure DevOps projects linked to a client, newest updated first, with counts per status (to do, in progress, done, canceled). Filter by status, tracker, project, assignee and date window. Data comes from DailyDashboard's issue sync (every 2 hours or on demand), not the live tracker. Returns a message when the client has no linked projects.

Parameters
  • clientIdstring
    required

    Client ID (or client name) whose linked projects to read.

  • statusstring

    Filter by status category (default all). 'open' is to do plus in progress.

    • all
    • open
    • todo
    • in_progress
    • done
    • canceled
  • providerstring

    Optional: only issues from this tracker.

    • jira
    • linear
    • monday
    • clickup
    • azuredevops
  • projectstring

    Optional project or team filter (key or part of the name).

  • assigneestring

    Optional assignee filter (part of the name); 'me' for the connected user's own issues.

  • sincestring

    ISO date or datetime; only issues updated on or after it (default: 14 days ago).

  • untilstring

    ISO date or datetime; only issues updated on or before it (default: now).

  • limitnumber

    Maximum issues to return (default 50, max 200).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getIssueTrackerActivity \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>"}'

Get DailyDashboard Usage Guidance

read

POST /api/v1/tools/getAppUsageGuidance

Return short how-to steps for one DailyDashboard feature area, such as client management, billing, templates or meeting transcripts.

Parameters
  • featurestring
    required
    • client-management
    • daily-work
    • templates
    • billing
    • settings
    • google-integration
    • meeting-transcripts
    • voice-notes
    • navigation
    • troubleshooting
Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getAppUsageGuidance \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"feature":"client-management"}'

Get Account Stats

read

POST /api/v1/tools/getCurrentUserStats

Return counts for the user's account: clients (with plan limit), tasks, follow-ups, meetings, or all of them.

Parameters
  • statTypestring
    required
    • clients
    • tasks
    • followups
    • meetings
    • all
Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getCurrentUserStats \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"statType":"clients"}'

Get Billing Data for All Clients

read

POST /api/v1/tools/getAllClientsBillingData

Summarize billable time across all clients for a preset date range or a custom start and end date. Returns hours and amounts per client and in total, with the individual time entries when includeTimeEntries is true. totalBilled and totalHours cover cash clients only; non-cash clients (paid in equity or deferred pay) are listed in nonCashClients with nonCashValue, their hours at their rate, totalled in nonCashValue and nonCashHours; personal projects are listed in projects with hours only. Time entries marked non-billable are worked but not charged: they are left out of totalHours and totalBilled and reported as nonBillableHours.

Parameters
  • dateRangestring
    • today
    • yesterday
    • this_week
    • last_week
    • this_month
    • last_month
    • this_year
    • last_year
    • year_to_date
  • startDatestring

    Custom range start date (YYYY-MM-DD)

  • endDatestring

    Custom range end date inclusive (YYYY-MM-DD)

  • includeTimeEntriesboolean

    Include detailed time entries

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getAllClientsBillingData \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Invoices

read

POST /api/v1/tools/getUserInvoices

List monthly invoice summaries, matching the Client Invoices dashboard, filtered by status, client, month or date range. Returns each invoice and month with totals, sent and paid amounts, expenses, credits and the outstanding portion, plus a count by status.

Parameters
  • statusstring

    Filter invoices by computed status (draft, generated, sent, partially_paid, paid, overdue: unpaid past its due date)

    • draft
    • generated
    • sent
    • partially_paid
    • paid
    • overdue
    • cancelled
    • all
  • clientIdstring

    Filter by specific client ID or name

  • dateRangestring

    Preset date range (e.g., this_month, last_month, this_year, last_year, year_to_date)

    • this_month
    • last_month
    • this_year
    • last_year
    • year_to_date
  • startDatestring

    Custom range start date (YYYY-MM-DD)

  • endDatestring

    Custom range end date inclusive (YYYY-MM-DD)

  • monthKeystring

    Specific month to retrieve (YYYY-MM)

  • includeAdjustmentsboolean

    Include monthly expenses/credits totals

  • limitnumber

    Maximum number of months to return (default 6, max 24)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getUserInvoices \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Outstanding Balances

read

POST /api/v1/tools/getOutstandingBalances

List outstanding balances owed by clients, optionally filtered by client and date range. Returns the balances and totals.

Parameters
  • clientIdstring

    Filter by specific client ID or name

  • includeArchivedboolean

    Also include the balance history of archived (deleted) clients when no clientId is given (default false)

  • startDatestring

    Start date for filtering (YYYY-MM-DD format)

  • endDatestring

    End date for filtering (YYYY-MM-DD format)

  • limitnumber

    Maximum number of records to return (default 50, max 200)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getOutstandingBalances \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Expenses and Credits

read

POST /api/v1/tools/getExpensesAndCredits

List expenses and credits, optionally filtered by client, type and date range. Returns the records and net totals; onInvoice is false for a record tracked against the client but kept off invoices.

Parameters
  • clientIdstring

    Filter by specific client ID or name

  • typestring

    Filter by type (expense or credit)

    • expense
    • credit
    • all
  • startDatestring

    Start date for filtering (YYYY-MM-DD format)

  • endDatestring

    End date for filtering (YYYY-MM-DD format)

  • limitnumber

    Maximum number of records to return (default 50, max 200)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getExpensesAndCredits \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Payments

read

POST /api/v1/tools/getPayments

List payments received, optionally filtered by client and date range. Returns the payments and totals.

Parameters
  • clientIdstring

    Filter by specific client ID or name

  • includeArchivedboolean

    Also include payments from archived (deleted) clients when no clientId is given (default false)

  • startDatestring

    Start date for filtering (YYYY-MM-DD format)

  • endDatestring

    End date for filtering (YYYY-MM-DD format)

  • limitnumber

    Maximum number of records to return (default 50, max 200)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getPayments \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

Get Meeting Transcript

read

POST /api/v1/tools/getMeetingTranscript

Read the text of the transcript linked to a meeting (a Google Doc transcript or an in-app meeting capture), one page at a time. Returns text, characters (total length), offset, returnedCharacters, hasMore and nextOffset (the offset of the following page). While the meeting is still being captured (transcript.status live) it returns the text captured so far, with live: true and offsetUnit "entries": offset and nextOffset then count caption entries rather than characters, and nextOffset is set even when hasMore is false, so calling again with offset = nextOffset during the call returns only what was said since the last call. When there is no transcript and no capture in progress, returns a message explaining why and no text.

Parameters
  • eventIdstring
    required

    The meeting's id (the id field of a meeting record).

  • offsetnumber

    Where to start reading (default 0): a character offset, or for a live capture (offsetUnit "entries") a caption entry number. Each page reports nextOffset for the following page.

  • maxCharactersnumber

    Maximum number of transcript characters in this page (default 24000, max 150000).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getMeetingTranscript \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"eventId":"<eventId>"}'

Get Meetings by Date Range

read

POST /api/v1/tools/getMeetingsByDateRange

List calendar meetings between startDate and endDate (inclusive), read live from DailyDashboard, across all clients or for one client. Each meeting includes timeStatus (past, in-progress or upcoming, relative to the current time in the user's time zone), summary (the calendar title), aiSummary (filled once a linked transcript has been processed) and a transcript object ({ linked, source, documentUrl, status: none|live|pending|processed|failed, processingError }). status live means the Meeting Capture extension is capturing the meeting right now (linked stays false until the capture ends; liveCapture gives entryCount and lastUpdatedAt) and the text captured so far can already be read. Returns the meetings with past, in-progress and upcoming counts.

Parameters
  • startDatestring
    required

    Start date for the meeting query (YYYY-MM-DD format). Required.

  • endDatestring
    required

    End date for the meeting query (YYYY-MM-DD format). Required.

  • clientIdstring

    Optional client ID or name to filter meetings for a specific client. If not provided, returns meetings across all clients.

  • includeSummariesboolean

    Whether to include AI summaries and meeting details (default: true)

  • limitnumber

    Maximum number of meetings to return (default: 100, max: 500)

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/getMeetingsByDateRange \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"startDate":"<startDate>","endDate":"<endDate>"}'

Process Meeting Transcript

write

POST /api/v1/tools/processMeetingTranscript

Run DailyDashboard's transcript pipeline for a meeting with a linked transcript: generates the AI summary, extracts tasks, decisions, follow-ups and initiatives as meeting recommendations, and adds the transcript to the client's knowledge base. Can take up to a minute. An already processed meeting is skipped unless force is true, which also regenerates the AI summary. A meeting whose transcript has a coverageWarning (the captured captions may belong to a different meeting) is refused unless confirmCoverageWarning is true. Returns the updated transcript status, the AI summary and counts of extracted items.

Parameters
  • eventIdstring
    required

    The meeting's id (the id field of a meeting record).

  • forceboolean

    Re-run processing even if the transcript was already processed, regenerating the AI summary (default false).

  • confirmCoverageWarningboolean

    true processes the transcript despite a transcript.coverageWarning, confirming it belongs to this meeting (default false).

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/processMeetingTranscript \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"eventId":"<eventId>"}'

Update Meeting

write

POST /api/v1/tools/updateMeeting

Edit an existing meeting or time entry by id: assign it to a different client, rename it, set the time spent on it in minutes, or mark its time non-billable (tracked but not charged). Changes only that meeting, not the client's email domains, and calendar sync keeps a client assigned this way. A meeting in a month locked for invoicing cannot be edited. Only the fields passed change. With confirmation true, saves the changes and returns them with the meeting's new state, with a note when a linked transcript was already processed under the previous client; otherwise changes nothing and returns a preview of the changes with a confirmation prompt.

Parameters
  • eventIdstring
    required

    The meeting's id (the id field of a meeting record).

  • clientIdstring

    The client to assign the meeting to: the client's ID or name.

  • titlestring

    New meeting title (max 500 characters).

  • timeSpentnumber

    Time spent on the meeting in minutes, 0 to 1440.

  • billableboolean

    false marks the time non-billable (tracked, not charged); true makes it billed time again.

  • confirmationboolean

    true saves the changes; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateMeeting \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"eventId":"<eventId>","confirmation":true}'

Append to Daily Notes

write

POST /api/v1/tools/appendToDailyNotes

Add content to a client's Daily Notes Google Doc under a date section (today in the user's time zone unless date is given), creating the date heading in the doc's own date format when that day has no section yet. Content takes '#', '##' and '###' headings, paragraphs, numbered ('1. ') and bulleted ('- ') list items, one per line; heading adds an optional subheading above it. Existing text stays as it is, and content already in that day's section is not added twice. With confirmation true, writes it and returns the date heading used, whether it was created and the doc's link; otherwise writes nothing and returns a preview with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • contentstring
    required

    The text to add (max 20000 characters): headings ('#', '##', '###'), paragraphs, numbered ('1. ') and bulleted ('- ') list items, one per line

  • datestring

    Optional date of the section (YYYY-MM-DD). Default: today in the user's time zone.

  • headingstring

    Optional subheading placed above the content inside the date section (max 200 characters).

  • confirmationboolean

    true writes to the document; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/appendToDailyNotes \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","content":"<content>","confirmation":true}'

Update Client Profile

write

POST /api/v1/tools/updateClientProfile

Overwrite high-level profile fields of an existing client: name, kind ("client" for a paying client, "project" for a personal project that is tracked but not invoiced), hourly rate, nonCash (true for a paying client that pays in equity or deferred pay: hours tracked and valued at the rate, not invoiced or counted in billed totals), identifiers, mission, vision, values, goals, summary, team overview, meeting cadence, task focus, notes, or the Budget section totals (totalBudget, spentBudget, remainingBudget). Only the fields in updates change. With confirmation true, saves the changes and returns the list of updated fields; otherwise changes nothing and returns a preview of the updated fields with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • updatesobject
    required

    Fields to update on the client profile

    • namestring
    • kindstring

      'client' for a paying client that is invoiced; 'project' for the user's own personal project, which is tracked but not invoiced

      • client
      • project
    • nonCashboolean

      true for a paying client paid in equity or deferred pay, not cash: its hours are still tracked and valued at its rate, but it is not invoiced or counted in billed totals (reported as non-cash value). false makes it a cash client again. Paying clients only.

    • ratenumber

      The client's hourly rate (null clears it). Non-cash clients keep a rate so their work is valued.

    • identifiersarray of strings
    • missionstring
    • visionstring
    • valuesstring
    • goalsstring
    • summarystring
    • teamOverviewstring
    • meetingCadencestring
    • taskFocusstring
    • notesstring
    • totalBudgetnumber

      The Budget section's total budget (null clears it).

    • spentBudgetnumber

      The Budget section's spent budget (null clears it).

    • remainingBudgetnumber

      The Budget section's remaining budget (null clears it).

  • confirmationboolean

    true saves the changes; false or omitted returns a preview without changing anything. Default false.

  • requestIdstring

    Optional identifier echoed back in the response.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateClientProfile \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","updates":{},"confirmation":true}'

Create Client Item

write

POST /api/v1/tools/createClientItem

Create one item for a client: a task, follow-up, decision, dictionary term, initiative, team member, resource link, event record, OKR objective, sprint goal, tech stack entry, budget line item, impact item or expense. An objective takes details { title, description?, owner?, period? (YYYY-MM or YYYY-Qn; defaults to the current quarter, or month with periodType "month"), keyResults?: [{ title, targetValue, startValue?, currentValue?, unit? }] }. A sprint goal takes details { title, description?, sprint?: "current" | "next" (default next) }. A tech stack item (tech_stack_item) takes details { field, value, url? }: field is a Tech Stack field (e.g. database, hostingProvider) to fill when empty, or any other label for a new custom item; a value already set stays as it is. A budget item (budget_item) takes details { name, amount, budgetType? }. An impact item (impact_item) takes details { text, kind?: "client" | "personal" (default client), url? }. An expense takes details { description, amount, spentDate? (YYYY-MM-DD, default today), category?, includeOnInvoice? }: a paying client's expense goes on the first unsent invoice from that month unless includeOnInvoice is false, and a personal project's is not invoiced. With confirmation true, saves the item and returns it; otherwise saves nothing and returns a preview with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • itemTypestring
    required

    Type of item to create

    • task
    • follow_up
    • decision
    • dictionary_term
    • initiative
    • team_member
    • resource_link
    • event_record
    • objective
    • sprint_goal
    • tech_stack_item
    • budget_item
    • impact_item
    • expense
  • detailsobject
    required

    Item-specific fields such as description, dueDate, assignedTeamMemberIds, term, definition, summary, attendees, etc.

    • descriptionstring
    • dueDatestring

      Target date or due date. Tasks: optional, YYYY-MM-DD or an ISO 8601 date-time. Follow-ups: ISO or natural language.

    • assignedTeamMemberIdsarray of strings
    • titlestring
    • termstring
    • definitionstring
    • linkstring
    • urlstring
    • summarystring
    • datestring
    • startTimestring
    • attendeesarray of strings
    • notesstring
    • ownerstring

      Objectives: who owns the objective.

    • periodstring

      Objectives: YYYY-MM (month) or YYYY-Qn (quarter).

    • periodTypestring

      Objectives: used when period is omitted (default quarter).

      • month
      • quarter
    • sprintstring

      Sprint goals: the sprint it is for (default next).

      • current
      • next
    • fieldstring

      Tech stack items: the Tech Stack field (e.g. database, hostingProvider) or a custom item's label.

    • valuestring

      Tech stack items: the technology, e.g. PostgreSQL.

    • namestring

      Budget items: the line item's name.

    • amountnumber

      Budget items and expenses: the amount in the client's currency.

    • budgetTypestring

      Budget items: the line item's type, e.g. Monthly, One-time.

    • textstring

      Impact items: the impact statement.

    • kindstring

      Impact items: the client's impact (default) or the consultant's personal impact.

      • client
      • personal
    • spentDatestring

      Expenses: the date the money was spent, YYYY-MM-DD (default today).

    • categorystring

      Expenses: software, travel, meals, office_equipment, professional_services, advertising, insurance, rent_utilities, bank_fees, taxes or other (default). Dictionary terms: an optional category.

    • includeOnInvoiceboolean

      Expenses for a paying client: false keeps it off invoices (default true). Ignored for personal projects, which are not invoiced.

    • keyResultsarray of objects

      Objectives: measurable key results.

  • clientNamestring

    Optional client name, used in the returned summary.

  • confirmationboolean

    true saves the item; false or omitted returns a preview without saving. Default false.

  • requestIdstring

    Optional identifier echoed back to correlate a preview with the save.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/createClientItem \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","itemType":"task","details":{},"confirmation":true}'

Create Client Items in Batch

write

POST /api/v1/tools/createClientItemsBatch

Create several items for one client in a single operation (any mix of tasks, follow-ups, decisions, dictionary terms, initiatives, team members, resource links, event records, OKR objectives, sprint goals, tech stack entries, budget line items, impact items and expenses; each item takes the same itemType and details as a single item). With confirmation true, saves them and returns a per-item result with success and failure counts; otherwise saves nothing and returns a preview of the list with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • itemsarray of objects
    required

    Ordered list of items to create.

    • itemTypestring
      required

      Type of item to create

      • task
      • follow_up
      • decision
      • dictionary_term
      • initiative
      • team_member
      • resource_link
      • event_record
      • objective
      • sprint_goal
      • tech_stack_item
      • budget_item
      • impact_item
      • expense
    • detailsobject

      Item-specific fields such as description, dueDate, assignedTeamMemberIds, term, definition, summary, attendees, etc.

    • requestIdstring

      Optional identifier to trace this item through the confirmation flow

  • clientNamestring

    Optional client name, used in the returned summary.

  • confirmationboolean

    true saves the whole list; false or omitted returns a preview without saving. Default false.

  • fromRecommendationIdstring

    Optional recommendation document ID. When provided, the categories of successfully created items will be automatically marked as processed on that recommendation.

  • requestIdstring

    Optional identifier echoed back to correlate a preview with the save.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/createClientItemsBatch \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","items":[],"confirmation":true}'

Update Task or Follow-up

write

POST /api/v1/tools/updateClientItem

Update an existing task or follow-up by id: mark it complete (completed: true), reopen it (completed: false), or edit its text, due date, assignees (follow-ups only), priority (tasks only) or link. Only the fields passed change. With confirmation true, saves the changes and returns them with the item's new state; otherwise changes nothing and returns a preview of the changes with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name

  • itemTypestring
    required

    Type of item to update

    • task
    • follow_up
  • itemIdstring
    required

    The task or follow-up id, as listed in the client's tasks or follow-ups.

  • completedboolean

    true marks the item done; false reopens it

  • textstring

    New wording for the task or follow-up

  • dueDatestring

    New due date (a follow-up's follow-up date), as YYYY-MM-DD or an ISO 8601 date-time (e.g. 2026-10-09T15:00:00Z; without an offset it is read in the user's time zone). Tasks only: an empty string removes the due date; a follow-up date cannot be removed.

  • assignedTeamMemberIdsarray of strings

    Follow-ups only: the complete new list of assignees, as team member ids or names. Replaces the current list; [] unassigns everyone.

  • prioritystring

    Tasks only: new priority

    • low
    • medium
    • high
  • linkstring

    New link URL; an empty string removes the link

  • confirmationboolean

    true saves the changes; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateClientItem \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","itemType":"task","itemId":"<itemId>","confirmation":true}'

Update Team Member

write

POST /api/v1/tools/updateTeamMember

Update a client's team member by id: name, title, role, email, phone, department or status ("departed" records that they left and keeps them in the client's history with their assignments; "active" reactivates them). The app shows one Title / role field, so a new title passed without a role also sets the role. Only the fields passed change. With confirmation true, saves the changes and returns them with the member's new state; otherwise changes nothing and returns a preview of the changes with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • memberIdstring
    required

    The team member id, as listed in the client's team.

  • namestring

    New full name

  • titlestring

    New job title; an empty string clears it and leaves the role as it is. The app shows one Title / role field, so a new title passed without a role also sets the role.

  • rolestring

    New role, shown in the app as the member's Title / role; an empty string clears it

  • emailstring

    New primary email, replacing the current primary address (other addresses stay); an empty string removes it

  • phonestring

    New phone number; an empty string clears it

  • departmentstring

    New department; an empty string clears it

  • statusstring

    "departed" records that the member has left; "active" reactivates them and clears the departure details

    • active
    • departed
  • departureReasonstring

    Departed members only: why they left

  • confirmationboolean

    true saves the changes; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateTeamMember \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","memberId":"<memberId>","confirmation":true}'

Remove Team Member

write

POST /api/v1/tools/removeTeamMember

Permanently delete a client's team member by id and unassign them from follow-ups, decisions and pending meeting recommendations; referral introductions keep their name. With confirmation true, deletes the member and returns the removed record and how many records they were unassigned from; otherwise deletes nothing and returns those counts with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • memberIdstring
    required

    The team member id, as listed in the client's team.

  • confirmationboolean

    true deletes the team member; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/removeTeamMember \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","memberId":"<memberId>","confirmation":true}'

Merge Team Members

write

POST /api/v1/tools/mergeTeamMembers

Merge a duplicate team member into another record of the same client. The duplicate's details fill the kept record's empty fields, emails and tags are combined, notes are kept side by side, and every follow-up, decision, pending meeting recommendation and referral introduction moves to the kept record; then the duplicate is deleted. A value that differs stays the kept record's and is listed in conflicts. With confirmation true, applies the merge and returns the merged member, the fields filled, the conflicts and how many records moved; otherwise changes nothing and returns the same details with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name.

  • keepMemberIdstring
    required

    Id of the team member record to keep, as listed in the client's team.

  • duplicateMemberIdstring
    required

    Id of the duplicate team member record to delete, as listed in the client's team.

  • confirmationboolean

    true applies the merge; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/mergeTeamMembers \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","keepMemberId":"<keepMemberId>","duplicateMemberId":"<duplicateMemberId>","confirmation":true}'

Update OKR Objective

write

POST /api/v1/tools/updateObjective

Update an existing OKR objective in a client's Goals section by id: check in key result progress (keyResults: [{ id, currentValue }]), set confidence (on_track / at_risk / off_track), grade it (status "achieved" or "missed", which locks in its score), reopen a graded one (status "active"), or edit its title, description or owner. Key results and confidence change only while the objective is active. Only the fields passed change. With confirmation true, saves the changes and returns them with the objective's new state; otherwise changes nothing and returns a preview of the changes with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID or name

  • objectiveIdstring
    required

    The objective id, as listed in the client's objectives.

  • keyResultsarray of objects

    Key result check-ins: the new current value of each key result to update.

    • idstring
      required

      Key result id, as listed in the objective's keyResults.

    • currentValuenumber
      required

      New current value

  • confidencestring

    In-period health check

    • on_track
    • at_risk
    • off_track
  • statusstring

    achieved / missed grades the objective and locks its score; active reopens a graded objective

    • active
    • achieved
    • missed
  • titlestring

    New objective title

  • descriptionstring

    New description (empty string clears it)

  • ownerstring

    New owner (empty string clears it)

  • confirmationboolean

    true saves the changes; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateObjective \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","objectiveId":"<objectiveId>","confirmation":true}'

Update Recommendation Status

write

POST /api/v1/tools/updateRecommendationStatus

Mark AI meeting recommendations for a client as processed or dismissed: one recommendation or all pending ones, for all or selected categories. With confirmation true, applies the change and returns how many items were updated; otherwise changes nothing and returns the number of items affected with a confirmation prompt.

Parameters
  • clientIdstring
    required

    The client's ID

  • actionstring
    required

    The action to take on the recommendations.

    • processed
    • dismissed
  • recommendationIdstring

    Optional specific recommendation document ID. Omit to target all pending recommendations for the client.

  • categoriesarray of strings

    Optional list of recommendation categories to update. Omit to target all categories.

    • tasks
    • initiatives
    • decisions
    • followUp
    • dictionary
    • teamMembers
    • objectives
    • sprintGoals
  • confirmationboolean

    true applies the change; false or omitted returns a preview without changing anything. Default false.

Example
curl -X POST https://dailydashboard.ai/api/v1/tools/updateRecommendationStatus \
  -H "x-api-key: $DAILYDASHBOARD_API_KEY" \
  -H "content-type: application/json" \
  -d '{"clientId":"<clientId>","action":"processed","confirmation":true}'

Support

Questions or problems with the API? Email support@dailydashboard.ai. Prefer to work in Claude? See the Claude connector.