Browse all documentation

Accept, dismiss or complete a fix

Apply a fix action. Completion saves the before snapshot and schedules the after comparison.

POST/api/v1/brands/{brandId}/fixes/{fixId}/{action}write

Call the corresponding update_fix MCP tool with JSON arguments. Supply brandId and other path values as named arguments when the endpoint has them.

Request details

Required scope: A valid write token.

Request example
curl --request POST \
  --url "https://searchseal.com/api/v1/brands/b7e4c2a0-5d1f-4c8e-9a3b-2f6d8e1c4a70/fixes/f5c2e8a1-9d3b-4e7f-a0c6-1b4d7e9f2a38/done" \
  --header "Authorization: Bearer $SEARCHSEAL_TOKEN"

An open fix accepts accept or dismiss. An accepted fix accepts done or dismiss.

Repeating an action after its target state is reached returns 200 without another state change.

Unsupported transitions or concurrent updates return 409 conflict. Use the dashboard to reopen a fix.

Request parameters

NameLocationRequiredTypeDescription
brandIdpathYesuuidAn active brand ID returned by the brand list.
fixIdpathYesuuidUnique identifier for the fix.
actionpathYes"accept" | "dismiss" | "done"Action to apply to the current fix state.

Response fields

Response body example
{
  "id": "f5c2e8a1-9d3b-4e7f-a0c6-1b4d7e9f2a38",
  "kind": "improve_page",
  "kindLabel": "Improve a page",
  "status": "done",
  "impact": "high",
  "title": "Add a rates and inclusions table to the villas page",
  "why": "AI Overview answering “best boutique hotel in ubud”",
  "pageUrl": "https://example.com/villas",
  "engine": "google_aio",
  "questionId": "e3a9d1e2-7b4c-4f60-8e2a-9c1d5b7f3e21",
  "createdAt": "2026-09-20T01:00:00.000Z",
  "doneAt": "2026-09-25T04:10:00.000Z",
  "instruction": "Add a table with each villa type, its nightly rate and what it includes.",
  "draft": "| Villa | From (IDR/night) | Includes |\n|---|---|---|\n| Garden | 2,100,000 | Breakfast |",
  "evidence": null,
  "source": null,
  "questions": [
    {
      "id": "e3a9d1e2-7b4c-4f60-8e2a-9c1d5b7f3e21",
      "text": "best boutique hotel in ubud"
    }
  ],
  "proof": {
    "metric": "visibility",
    "before": 0.21,
    "after": null,
    "change": null,
    "comparable": false,
    "reason": "waiting_for_after",
    "doneAt": "2026-09-25T04:10:00.000Z",
    "dueAt": "2026-10-09T04:10:00.000Z"
  },
  "meta": {
    "generatedAt": "2026-09-26T08:15:02.114Z",
    "timeZone": "Asia/Jakarta"
  }
}
FieldTypeDescription
…FixUpdated fix detail, with the same fields as the individual fix response.

Successful REST responses from this endpoint include the shown meta fields. Read about data-through dates.

Possible errors

  • 400 invalid_request — An input failed validation. Field details may appear in errors.
  • 401 unauthorized — Authentication failed because the token is absent, unrecognized or revoked.
  • 403 forbidden — Account access or token permissions do not allow this request. Check the message for the cause.
  • 404 not_found — The resource is missing or unavailable to this account, including inactive brands.
  • 409 conflict — The fix action is invalid for its current state, or another update changed it concurrently.
  • 429 rate_limited — A quota was reached or could not be checked. Wait the Retry-After delay before retrying.
  • 500 server_error — The server failed to complete the operation.

For the shared error format, see status codes, quotas and retries. Next endpoint: List proofs.