seo-connect

POST /v1/seo-connection/offers/orders/{orderId}/placement

Where a bought link went live; watched by link watch from now on.

All seo-connect endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks sites.create; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/seo-connection/offers/orders/{orderId}/placement \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "url": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Needs the seo.run scope, and a paid link or citation order. The page must be on another website. The link (page, the order's target address and anchor) joins the site's watched links, checked like every other watched link.

Parameters

NameTypeRequiredWhat it is
orderId (path)UuidYes—

Request body

NameTypeRequiredWhat it is
urlstringYes—

Response

NameTypeRequiredWhat it is
idstringYes—
offerSeoOfferKeyYes—
ledgerstringYes—
productstringYes—
kindstringYes—
labelstringYes—
contextobjectYes—
urlstringYesWhere the order continues — opened in a new tab.
statusstring<opened, basket, awaiting_payment, payment_failed, paid, brief_needed, in_progress, delivered, done, disputed, cancelled, refunded, expired>Yes—
total_minorobjectNo—
tax_minorobjectNo—
currencystringNo—
order_idstringNo—
sale_idstringNo—
placement_urlstringNo—
watchedbooleanYes—
created_atstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422