visibility

PUT /v1/visibility/targets/{targetId}/products

Set the products to price-track, and the seller names to look for.

Всички крайни точки в visibility

Упълномощаване

Изпратете API ключ като носител (bearer token). Тази точка за достъп не указва конкретно разрешение в спецификацията, затова дайте на ключа си най-малкото необходимо и проверете отговора, вместо да правите предположения.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X PUT https://api.zinndigital.com/v1/visibility/targets/{targetId}/products \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

The products and the merchant names are set together because they are only useful together. With products and no seller name we can read the shelf and list who is on it, but we cannot say whether the customer is one of them — the audit reports `product_seller_unknown` and the score is `null`, which is honest rather than a claim that they are missing from Google Shopping. Nothing infers a seller name from the customer's domain. Measured against a live Google Shopping response: every listing carries a `seller` name and a **null** `domain`, so a near-match on a trading name is the only thing a guess could use — and a wrong one would report a stranger's price as the customer's own, on a screen they pay for, with nothing downstream able to detect it. Sending more products than the plan allows is refused with `422` naming the allowance. It is **not** truncated: silently auditing the first ten of two hundred reads as a complete list on the very screen the customer checks.

Параметри

ИмеТипЗадължителноКакво представлява
targetId (path)UuidДаThe watched domain's id.

Тяло на заявката

ИмеТипЗадължителноКакво представлява
productsTrackedProduct[]Не
merchant_namesstring[]Не

Отговор

ИмеТипЗадължителноКакво представлява
idUuidДаUUIDv7 identifier — sortable by creation time (docs/02 §8).
domainstringДаThe hostname
labelstringНеThe customer's own label for this domain.
brandstringНеThe trading name to look for in an answer engine's reply. Genuinely separate from the domain — an answer that recommends a business by name without printing its URL has still me…
categorystringНеWhat this business sells, in the customer's own words. The questions asked of the answer engines are built from it, so it is the single field that decides whether an AI-visibili…
marketstringНеWhere the business sells. Used with `category` to build the questions.
is_externalbooleanДаTrue when this is not a domain hosted with us — a competitor or a prospect. Only external targets count against the plan's allowance.
site_idstringНеThe site this target corresponds to, when it is one of ours.
kindsVisibilityAuditKind[]Да
cadence_daysintegerДаDays between scheduled audits. `0` means paused — **not** deleted. History and settings survive and it resumes with no further action.
next_due_atstringНе
last_audit_atstringНе
review_profilesReviewProfile[]Не
productsTrackedProduct[]НеThe products this organisation has asked us to price-track.
merchant_namesstring[]НеHow this business appears as a **seller** on the marketplaces. Confirmed by the customer and never inferred: Google Shopping publishes a seller name and no domain on its listing…
keywordsTrackedKeyword[]НеThe search phrases this organisation tracks its position for. Customer-supplied and never derived: asking a vendor which phrases a domain already ranks for would return exactly…

Грешки, които този крайpoint може да върне

401 · 403 · 404 · 422