Intent

Keywords Add

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.
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

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

keywordsstring[] 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

Successful Response

Changes

No recorded changes to this operation across all 2 revisions of this API.