---
title: "Add prompts"
method: POST
path: "/api/mcp/projects/{projectId}/prompts"
tags: ["Prompts"]
---

# Add prompts

`POST /api/mcp/projects/{projectId}/prompts`

## Request

- Base URL: `https://app.searchable.com`
- URL: `https://app.searchable.com/api/mcp/projects/{projectId}/prompts`
- Auth: HTTP bearer

Add 1-10 prompts in one call. They're tracked straight away (`isTracked: true`), as when you add prompts in the app: the project's next scheduled run checks them, and they count toward the prompt allowance. The whole batch is checked against the allowance first; one that does not fit adds nothing and returns 403 `quota_exceeded`, so archive some prompts first or add fewer. Requires a connection minted with the `prompt:draft` capability (not the bare `write` scope). NOT atomic across items: each prompt is created independently, so a failure partway through (for example another write taking the allowance's last room) leaves the earlier items created (`created` in the response says how many). Any `topicIds` must belong to the same project as the prompt; one that does not is refused with 404 `not_found`, indistinguishable from a topic id that does not exist. Supports `Idempotency-Key` replay; a reused key with a different body returns 409 `idempotency_conflict`.

## Path parameters

- `projectId` string, uuid, required

## Headers

- `Idempotency-Key` string

## Request body

- AddPromptsRequest
  - `prompts` AddPromptItem[], required
    - `text` string, required
    - `intentCategory` 'informational' | 'commercial' | 'transactional' | 'navigational' | 'post_purchase'
    - `isBranded` boolean
    - `topicIds` string[]

## Response `200`

Prompts added.

- AddPromptsResponse
  - `prompts` AddPromptDraft[], required
    - `id` string, uuid, required
    - `text` string, required
    - `topicId` string, nullable
    - `topicName` string, nullable
    - `topics` object[], required
      - `id` string, required
      - `name` string, required
    - `lastUpdated` string, required
    - `createdAt` string, date-time, nullable
    - `isFromOnboarding` boolean, nullable
    - `isTracked` boolean, nullable: `false` for every draft this endpoint creates — call the tracking endpoint to turn it on.
    - `locations` object[], required
      - `id` string, required
      - `countryCode` string, required
      - `city` string, nullable
      - `region` string, nullable
      - `latitude` number, nullable
      - `longitude` number, nullable
    - `fallbackLocation` unknown
    - `usesFallbackLocation` boolean, required
    - `projectId` string, uuid, nullable
    - `intentCategory` string, nullable
    - `promptType` string, nullable
    - `isBranded` boolean, nullable
    - `keywordSearchVolume` integer, nullable
    - `keywordDifficulty` integer, nullable
    - `currentRevision` integer, required: Optimistic-concurrency counter — pass as `If-Match` on a subsequent PATCH to detect a concurrent change without a second fetch.
    - `updatedAt` string, date-time, nullable
  - `created` integer, required
  - `success` boolean, required

## Other responses

- `400`: Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `401`: Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `403`: Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `404`: Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `409`: Another request with the same `Idempotency-Key` is still executing. `Retry-After` (5 seconds) is always present — retry with the SAME key once it elapses.
- `429`: Rate limited. Usually the per-API-key REST limit (600 requests/minute); on Google-backed endpoints it can also relay an upstream Google rate limit. `Retry-After` (seconds) is present when the limit was applied by Searchable's own rate limiter; it may be absent when an upstream provider rate-limits.

## Changes

- **2026-11-03** `28a5e2a65cd3`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/searchable/apis/searchable-rest-api/changes/api/mcp/projects/:projectId/prompts/post.md)

---

[API](https://skmtc.dev/searchable/apis/searchable-rest-api.md) - [All operations](https://skmtc.dev/searchable/apis/searchable-rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/searchable/apis/searchable-rest-api/revisions/a1cc70e46e73?raw)