Skip to content

Commit 0bc1666

Browse files
calvarezgclaude
andcommitted
triage: clarify sentiment-overview 503 description (review feedback)
The 503 is reachable and genuinely PostgREST-related (authorizeOrg returns it when the PostgREST client is absent, during brand->workspace resolution, before any Semrush call), but "not configured for this deployment" read as misleading on a Semrush-backed endpoint. Reword to state the actual condition and why. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 2538034 commit 0bc1666

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

docs/index.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/openapi/serenity-api.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1246,7 +1246,7 @@ v2-serenity-brand-presence-sentiment-overview:
12461246
application/json:
12471247
schema: { $ref: './schemas.yaml#/SerenityErrorResponse' }
12481248
'503':
1249-
description: PostgREST client not configured for this deployment.
1249+
description: PostgREST client not available (required to resolve the brand's Semrush workspace before the element call).
12501250
content:
12511251
application/json:
12521252
schema: { $ref: './schemas.yaml#/SerenityErrorResponse' }

0 commit comments

Comments
 (0)