Content

Dismiss, restore or publish

Move an opportunity: dismiss one that isn't relevant, restore a dismissed one, or mark its draft published so the platform starts measuring the effect.

POSThttps://api.vidrys.com/v1/projects/{project_id}/content-assets/{asset_id}/state

Plan: Scale and Custom
Key: read-and-write
Rate cost: 1 unit
MCP tool: set_content_asset_state

mark_published only works on an opportunity whose draft is ready, and it starts verification — from then on, each prompt and engine is re-measured against the published page.

A move the workflow doesn't allow answers 409 conflict and names the states involved.

Dismiss, restore or publish

curl --request POST \
  --url "https://api.vidrys.com/v1/projects/{project_id}/content-assets/{asset_id}/state" \
  --header "Authorization: Bearer $VIDRYS_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "action": "mark_published"
}'

200 · success

{
  "ok": true,
  "id": "d4e5f6a7-8b9c-40d1-92e3-4f5a6b7c8d9e",
  "status": "verifying",
  "message": null
}

Authorization

Sent as a header on every request.

Authorizationstringrequired

A Vidrys API key, sent as Bearer vidrys_sk_…. This call changes data, so the key must be read-and-write. See Authentication.

Path parameters

project_idstringrequired

The project's id, from List projects.

asset_idstringrequired

The opportunity's id, from List content opportunities.

Body

application/json

actionenum<string>required

What to do.

Values:dismissrestoremark_published

Response · 200

application/json

okboolean

True when the change was made.

idstringnullable

The item changed.

statusstringnullable

Its state or status after the change.

messagestringnullable

Reserved. Null today.

Errors

403 write_not_allowed	The key is read-only. Writes need a read-and-write key, and read-and-write keys need Scale or Custom.
409 conflict	The item isn't in a state that allows the change — for example marking an opportunity published before it has a draft, or drafting one that is already being drafted.
404 not_found	The project or item doesn't exist in this workspace. A project from another workspace also returns 404, never 403.
422 invalid_request	A parameter or body field is missing or has the wrong type or value. The message names the field. Also returned when a write would pass the plan's prompt limit.
401 unauthorized	No key was sent, or the key is unknown, revoked or expired, or the member who created it has left the workspace or been deactivated.
402 plan_required	The workspace's plan doesn't include API access. It's included on Grow, Scale and Custom.
403 workspace_not_approved	The workspace is still waiting for approval, or wasn't approved.
429 rate_limited	Too many requests this minute. Wait for the number of seconds in the `Retry-After` header, then retry.

Every code, and what to retry, is in Errors.