seo-connect

POST `/v1/seo-connection/work-log`

The plugin reports what it did on the site, for the client's report.

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/work-log \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "entries": <SeoWorkEntryInput[]> }'

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

Zinn® SEO stage E5. Counts per day and kind (never page titles or content), idempotent on each entry's id: a night sent twice is the same rows. At most 500 entries per call; the whole call is refused on the first bad entry, with its index. Feeds the "Work done on the site" section of white-label client reports. Needs the seo.run scope.

Request body

Name	Type	Required	What it is
`entries`	`SeoWorkEntryInput[]`	Yes	—

Response

Name	Type	Required	What it is
`accepted`	`integer`	Yes	—

Errors this endpoint can return

401 · 403 · 422

POST /v1/seo-connection/work-log