Resource Reference

This page documents the human-readable shape of the v1 Deck Public API. The machine-readable contract at /openapi is the complete source for endpoint methods, request bodies, filters, and response schemas.

Endpoint summary

/me

Use this endpoint to confirm that your key works and see the identity Deck resolved from it.

Response fields

/themes

Lists themes for the authenticated organization.

Query parameters

Theme fields

/insights

Lists insights for the authenticated organization.

Query parameters

Supported categories

• PAIN_POINTS
• DELIGHTS
• GENERAL_FEEDBACK
• FEATURE_REQUESTS
• USABILITY_ISSUES
• BUGS_AND_ERRORS

Insight list fields

/insights/{insightId}

Returns a single insight with richer source metadata.

Additional fields include:

• feedback_id
• contact_id
• user_email
• user_name
• interview_date

/projects

Lists Projects for the authenticated organization.

POST /projects creates a Deck-side Project and seeds the canonical Overview, Evidence, and Success Metrics sections. Required body: title. Optional body fields: description, status, initiative_id, and owner_id.

Query parameters

Supported statuses

• not_started
• in_progress
• completed
• archived

Project fields

/projects/{projectId}

Returns a single Project plus structured document sections and evidence references.

PATCH /projects/{projectId} updates Project metadata: title, description, status, initiative_id, owner_id, start_date, and target_date.

DELETE /projects/{projectId} soft-deletes the Project by archiving it. It does not delete or mutate Jira or Linear artifacts.

Additional fields:

• sections
• evidence_references
• external_links
• latest_evidence_story

Project sections include Overview, Evidence, and Success Metrics content when present.

/initiatives

Lists initiatives for the authenticated organization.

Query parameters

Supported statuses

• draft
• exploring
• building
• ready_to_act
• completed
• archived

Initiative fields

/initiatives/{initiativeId}

Returns a single initiative plus structured content sections.

Additional fields:

• sections
• last_generated_at

Each section includes:

• key
• content
• updated_at

Build write surfaces

Build writes are action-based and strictly bounded.

Required on every mutation:

• Idempotency-Key header (1-128 chars)
• one action payload per request
• org policy that allows write scope for the key owner

Explicit non-goals:

• backlog generation endpoints
• standalone story generation endpoints outside approved Build actions
• arbitrary delete endpoints
• third-party Jira or Linear artifact creation

/build/projects

Executes one Project mutation action.

Supported actions

link_external_artifact stores Deck-side Jira or Linear metadata for artifacts that already exist. It does not create or modify provider artifacts.

/build/initiatives

Executes one initiative mutation action.

Supported actions

/build/opportunities

Executes one opportunity mutation action.

Supported actions

Idempotency behavior

• Same key + same normalized payload returns the original response with idempotency.replayed=true
• Same key + different payload returns 409 IDEMPOTENCY_CONFLICT
• Reusing the same key while the original matching request is still running also returns 409 IDEMPOTENCY_CONFLICT

/subthemes

Lists subthemes synthesized from theme-level or segment-level analysis.

Query parameters

Subtheme fields

/subthemes/{subthemeId}

Returns full synthesized subtheme detail.

Additional fields:

• insight_ids
• blocks
• theme
• related_subthemes

Use this endpoint when you need more than the summary list and want the full subtheme context.

/competitors

Reads and writes the in-app Competitors graph. The workspace must have Competitors enabled. Otherwise Deck returns 403 FEATURE_NOT_AVAILABLE.

This graph is separate from your first-party themes and insights. List responses include graph status (empty, importing, running, ready, or failed), optional last_job, and competitor { id, name, domain } rows.

The Public API does not enable or disable Competitors, and it does not delete a tracked competitor. Those actions live in Settings → Competitors.

Writes require write scope and an Idempotency-Key header (1–128 characters). Members can start research, add a competitor, and promote a finding. Only organization admins can change the check-in schedule (POST /competitors/checkins returns 403 ROLE_NOT_ALLOWED for members).

POST /competitors/research

Merges the posted competitors with the set you already track and appends new reviews onto the published graph — the same behavior as adding a competitor in the app. An empty competitors array is 400. Research that is already running is 409 CONFLICT. A successful start returns 202 with { job_id, status }.

{
  "competitors": [{ "name": "Rival", "website": "rival.com" }],
  "reviews_per_source": 30
}

reviews_per_source is optional (10–100). The default is 30.

Poll GET /competitors/research/{jobId} until the job is ready or failed. If the workspace does not have enough credits, the job response is still HTTP 200 with error_code: CREDIT_LIMIT_EXCEEDED. The last published graph stays visible while research runs.

POST /competitors/promote

Promotes a competitor subtheme or opportunity teaser into Opportunity Backlog.

{
  "source_type": "subtheme",
  "source_id": "…",
  "title": "Fix onboarding",
  "include_first_party_feedback": true
}

source_type is subtheme or opportunity_teaser. Promoting the same source again returns the existing backlog item (existing: true) instead of creating a duplicate.

GET /competitors/checkins

Lists check-in runs newest first. The response is { data, pagination }. Pass the last run id as cursor. limit is 1–100 and defaults to 50.

Each run includes status, cadence, timestamps, and a snapshot. Empty runs store { "changed": false } only. When the snapshot has diffs, rank closer to 0 means the theme moved up; an impactScore increase of 1 means the opportunity is more valuable.

GET /competitors/checkins/latest

Returns the most recent check-in run, or null if none exist.

POST /competitors/checkins

Organization admins enable or disable periodic check-ins. This does not start a scrape immediately.

{
  "enabled": true,
  "cadence": "monthly"
}

cadence is weekly, monthly, or quarterly (7 / 30 / 90 elapsed days). If you enable check-ins without a cadence, Deck uses monthly. Check-ins require Competitors to be on.

Pagination

Cursor pagination

Used by:

• themes
• insights
• projects
• initiatives
• competitor opportunity-teaser insights
• competitor check-in runs

Response shape:

{
  "pagination": {
    "next_cursor": "opaque-string-or-null",
    "has_more": true
  }
}

Offset pagination

Used by:

• subthemes

Response shape:

{
  "pagination": {
    "total": 120,
    "has_more": true,
    "offset": 0,
    "limit": 50
  }
}

OpenAPI spec

The latest API contract is available at:

/api/v1/openapi

Use it when you want the exact field types or need to generate a client.

Related pages

• Public API
• Authentication and Access
• Examples