---
title: "Keywords Add"
method: POST
path: "/intent/keywords/add"
tags: ["Intent"]
---

# Keywords Add

`POST /intent/keywords/add`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/intent/keywords/add`
- Auth: HTTP bearer

Bulk-add plain compete-tracking keyword rows (web-UI "Add keywords" parity).

Thin public proxy over the SAME handler the graph8 web UI's Buyer Intent >
Keywords bulk-add uses (``POST /intent/keywords/add-keywords`` internally).
One deliberate strictness on top of the UI path: entries are trimmed of
leading/trailing whitespace before saving (the UI screen saves them raw).
Everything else matches the UI path:

- Keywords are stored lowercased; the response carries the stored text.
- A keyword that already exists for this org + ``signal_type`` (and is not
  soft-deleted) is skipped silently by the handler; this route reports it
  as ``skipped`` with reason ``already_exists``. Soft-deleted keywords can
  be re-added.
- For ``signal_type='intent'`` each NEWLY created keyword fires a
  background SERP fetch that seeds its URL set asynchronously - URLs and
  resolved contacts/companies appear later, not in this response.
- Unlike ``create-from-search`` this saves the plain phrase only (no
  search seeding, no ``search_filters``); use
  ``/keywords/{id}/filters`` afterwards to set per-keyword filters.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- KeywordsAddRequest
  - `keywords` string[], required: 1-50 keyword phrases to add as plain compete-tracking rows. Stored lowercased. Empty / whitespace-only entries and in-request duplicates (case-insensitive, trimmed) are skipped, not saved twice.
  - `signal_type` 'intent' | 'jobs' | 'job_changes': Signal source discriminator, same vocabulary as the web UI: 'intent' (default, buyer-intent tracking), 'jobs', or 'job_changes'.

## Response `200`

Successful Response

- ApiResponseKeywordsAddResponse
  - `data` KeywordsAddResponse, required
    - `created` KeywordAddedItem[]
      - `id` string, required
      - `keyword` string, required: Stored (lowercased) keyword text.
      - `signal_type` string, required
      - `created_at` string, date-time, nullable
    - `skipped` KeywordsAddSkippedItem[]
      - `keyword` string, required
      - `reason` string, required: 'empty' | 'duplicate_in_request' | 'already_exists'
    - `created_count` integer
    - `skipped_count` integer
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/89fc11143b70?raw)