Repository navigation
fix(note): post Notes to /api/v1/comment/feed/ (trailing slash) - #20
Open
nori-sessions[bot] wants to merge 1 commit into
Open
nori-sessions[bot] wants to merge 1 commit into
nori-sessions[bot] wants to merge 1 commit into
Conversation
Substack's Cloudflare edge answers POST /api/v1/comment/feed (no slash) with a 403 HTML error page for every caller, signed in or not; the request never reaches Substack. With the slash it reaches Substack's app (checked 2026-10-22 with an invalid body: 400 "Please add a comment or an attachment."). The first live growth-ops Note (@theahura) failed this way. Co-Authored-By: Nori <contact@tilework.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
note createposted toPOST https://substack.com/api/v1/comment/feed. Substack's Cloudflare edge answers that path with a 403 HTML page ("Error - Substack / Something has gone terribly wrong") for every caller, with or without cookies or a browser User-Agent. The 403 response has nox-powered-by: Express/x-served-by: Substackheaders, so the request never reached Substack's app./api/v1/comment/feed/, with the slash (the path jakub-k-slys/substack-api uses), reaches the app. I checked this read-only on 2026-10-22 with an invalid body: 400{"error":"Please add a comment or an attachment."}.This blocked the first live growth-ops Substack Note (@theahura, transcript 01a1608d-ba7f-7311-a7d0-39c60e3f2e79).
endpoint-coveragenow expects the trailing slash; all 65 tests pass; lint is clean.dist/is rebuilt.🤖 Generated with Claude Code