Skip to content

fix: print the API error body after the 404 endpoint hints in apify api - #1492

Closed
Pijukatel wants to merge 1 commit into
masterfrom
fix/api-404-body-after-hint
Closed

Pijukatel wants to merge 1 commit into
masterfrom
fix/api-404-body-after-hint

Conversation

@Pijukatel

Copy link
Copy Markdown
Contributor
  • On a 404, apify api printed the response body first and then the "Did you mean" endpoint list, which pushed the API's own error out of view. For a record-not-found-style 404 (e.g. a schedule action naming an unknown Actor) that body is the part that says what is actually wrong.
  • Print the hint first and the body last; the body still goes to stdout so apify api ... | jq keeps working on failures.
  • Extends the 404 suggestions test to assert the body is still printed.

🤖 Generated with Claude Code

https://claude.ai/code/session_015VTFswSQJstnQ6r8QeqfgK


Generated by Claude Code

The "Did you mean" list came after the body and pushed the API's own error, which usually says what is
actually wrong (an unknown record rather than an unknown endpoint), out of view.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015VTFswSQJstnQ6r8QeqfgK
@Pijukatel Pijukatel closed this Oct 12, 2026
@Pijukatel
Pijukatel deleted the fix/api-404-body-after-hint branch October 12, 2026 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant