Get fix
Read a fix’s details, suggested draft, supporting evidence, tracked questions and before-and-after comparison.
GET
/api/v1/brands/{brandId}/fixes/{fixId}readCall the corresponding get_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 read or write token.
Request example
curl --request GET \
--url "https://searchseal.com/api/v1/brands/b7e4c2a0-5d1f-4c8e-9a3b-2f6d8e1c4a70/fixes/f5c2e8a1-9d3b-4e7f-a0c6-1b4d7e9f2a38" \
--header "Authorization: Bearer $SEARCHSEAL_TOKEN"Request parameters
| Name | Location | Required | Type | Description |
|---|---|---|---|---|
brandId | path | Yes | uuid | An active brand ID returned by the brand list. |
fixId | path | Yes | uuid | Unique identifier for the fix. |
Response fields
Response body example
{
"id": "f5c2e8a1-9d3b-4e7f-a0c6-1b4d7e9f2a38",
"kind": "improve_page",
"kindLabel": "Improve a page",
"status": "accepted",
"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": null,
"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": null,
"meta": {
"generatedAt": "2026-09-26T08:15:02.114Z",
"timeZone": "Asia/Jakarta"
}
}| Field | Type | Description |
|---|---|---|
… | Includes all fields returned by the fix list. | |
instruction | string | null | Saved instructions for making the change. |
draft | string | null | Proposed copy based on brand facts and source material. Review before publishing. |
evidence | object | null | Search-fix evidence includes summary, query, clicks, impressions, position, from and through; answer fixes have no search-evidence object. Site-access fixes carry source: "access", summary, checkedAt and either bots (each blocked bot’s token and blocks, with url, robotsUrl, line and lineNumber) or page (url, finalUrl, httpStatus, badSince, directives and canonical), plus resolution when a re-check found it fixed and reopenedAt when it came back. Page-check fixes carry source: "audit", summary, checkedAt, auditId, checkId, url, score and impact, with the same resolution and reopenedAt. |
source | object | null | Returned source URL as { url, title, domain }, when available. Explicit citation status is unknown. |
questions | object[] | Questions associated with the fix group, each as { id, text }. |
proof | object | null | Saved before-and-after comparison for a completed fix, using the fields from /proofs; otherwise null. |
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 inerrors.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.429 rate_limited— A quota was reached or could not be checked. Wait theRetry-Afterdelay 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: Accept, dismiss or complete a fix.