Fix claim URL path to /monitor/claim and flip default endpoint to HTTPS#14
Merged
Merged
Conversation
Two minor URL corrections that should have landed together in #13: - Claim URL: the SaaS claim page is at /monitor/claim alongside the other Pulse portal routes, not at /claim on the root. - Default endpoint: was http://api.patchstack.com (HTTP). Browsers will redirect to HTTPS at the server, but printing an http:// link in the build log is sloppy. Tests updated; help text and README brought in line. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mariojgt
approved these changes
May 13, 2026
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
2 participants
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.
Summary
Two minor URL corrections that should have landed together in #13 but were spotted afterwards:
/monitor/claimalongside the other Pulse portal routes (/monitor/pulse/manifest/{uuid}etc), not at/claimon the root.PATCHSTACK_ENDPOINTwashttp://api.patchstack.com/monitor/pulse/manifest. Servers redirect to HTTPS at the edge, but printing anhttp://link in the build log is sloppy and makes the connector look misconfigured.What changes
src/client.ts:DEFAULT_ENDPOINT→https://api.patchstack.com/....buildClaimUrlappends/monitor/claiminstead of/claim. Docblock updated.src/cli.ts: help text shows the new HTTPS default.README.md: same edit on the environment-variable documentation.tests/client.test.ts: every/claim?site=assertion updated to/monitor/claim?site=. Suite 51 green.Verification
npx tsc --noEmit— cleannpx vitest run— 51/51 passingdist/rebuilt with the corrected paths and schemeImpact on consumers
Anyone using the default endpoint without overriding it will now see
https://instead ofhttp://— should be transparent because the server redirects anyway. Anyone overriding the endpoint (staging, ngrok, local) is unaffected because the connector still uses whatever scheme the override specifies.The claim URL change is more visible: existing v0.2.x output prints
https://api.patchstack.com/claim?site=...which will 404; once this ships in v0.3.0 (or 0.2.5, your call) the printed URL hits the right path.🤖 Generated with Claude Code