visibility

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

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

Alle visibility-eindpunten

Authenticatie

Stuur een API-sleutel mee als bearer token. Dit eindpunt vermeldt geen specifieke toestemming in de specificatie, dus geef uw sleutel de minimale rechten die nodig zijn en controleer het antwoord in plaats van zomaar wat aan te nemen.

Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.

Probeer het

Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.

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

Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console

Details

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.

Parameters

NaamTypeVerplichtWat dit is
targetId (path)UuidJaThe watched domain's id.

Aanvraaglichaam

NaamTypeVerplichtWat dit is
productsTrackedProduct[]Nee
merchant_namesstring[]Nee

Reactie

NaamTypeVerplichtWat dit is
idUuidJaUUIDv7 identifier — sortable by creation time (docs/02 §8).
domainstringJaThe hostname
labelstringNeeThe customer's own label for this domain.
brandstringNeeThe 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…
categorystringNeeWhat 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…
marketstringNeeWhere the business sells. Used with `category` to build the questions.
is_externalbooleanJaTrue when this is not a domain hosted with us — a competitor or a prospect. Only external targets count against the plan's allowance.
site_idstringNeeThe site this target corresponds to, when it is one of ours.
kindsVisibilityAuditKind[]Ja
cadence_daysintegerJaDays between scheduled audits. `0` means paused — **not** deleted. History and settings survive and it resumes with no further action.
next_due_atstringNee
last_audit_atstringNee
review_profilesReviewProfile[]Nee
productsTrackedProduct[]NeeThe products this organisation has asked us to price-track.
merchant_namesstring[]NeeHow 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[]NeeThe 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…

Fouten die dit eindpunt kan retourneren

401 · 403 · 404 · 422