chore: point key links at /api-credentials - #40
Merged
Conversation
lenz.io renamed /api-integration to /api-credentials: the page holds API keys AND OAuth connected apps, and the old path read like an integration landing page rather than a credentials manager. Touches the runtime strings users actually see — the 401 remediation hint, the missing-key error, and the three webhook-secret errors — plus _dashboard_url(), which `lenz login` OPENS IN A BROWSER, so it is the one that would visibly take someone to a redirect. Not urgent for anyone already installed: lenz.io keeps a permanent 302 from the old path precisely because published versions of this package hard-code it and can never be updated. This just stops new releases pointing at a redirect. openapi.json is deliberately untouched — it is generated from the Lenz repo via `make regen`, so it picks the new wording up on the next regeneration rather than being hand-edited here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016A7nD9KjjwujFHr17SBybh
lenzhq
added a commit
that referenced
this pull request
Aug 17, 2026
lenz.io renamed /api-integration to /api-credentials and now calls the page 'API credentials' rather than 'API Integration' — the page holds API keys AND OAuth connected apps. That text lives in the API description (lenz/api/public_api.py), which is upstream of this file. Generated with `make regen` against Lenz main at 8d058f71 (the merge commit of lenzhq/Lenz#279), so this reflects merged main rather than a branch. Diff is one line: the info.description blob, two path occurrences and two name occurrences. No other drift — the snapshot was otherwise already in sync. Deliberately NOT bundled into the code PR (#40): regenerating before the Lenz change merged would have published a spec naming a URL that still 404'd. Claude-Session: https://claude.ai/code/session_016A7nD9KjjwujFHr17SBybh Co-authored-by: Lenz <support@lenz.io> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
lenz.io renamed
/api-integration→/api-credentials. The page holds API keys and OAuth connected apps, and the old path read like an integration landing page rather than a credentials manager (it was the likeliest reason several B2B ad landing pages pointed their CTA there instead of the setup wizard).What changed
Runtime strings users actually see
errors.py— the 401 remediation hint attached to every auth errorclient.py— the missing-key errorwebhooks.py×3 — the webhook-secret errorsThe one that's visible as a redirect
cli/commands.py_dashboard_url()—lenz loginopens this in a browser, so it is the one place a user would watch the hop happen.Plus README, the FastAPI webhook example, and two tests.
Not urgent for anyone already installed
lenz.io keeps a permanent 302 from the old path, specifically because published versions of this package hard-code
/api-integrationin runtime strings and can never be updated. Nothing breaks; this just stops new releases pointing at a redirect.openapi.json is deliberately untouched
It is generated from the Lenz repo (
make regen→manage.py emit_openapi), and the upstream description change is in the corresponding Lenz PR. Regenerating here before that merges would produce a file that doesn't match. Follow-up: runmake regenonce the Lenz change lands.Rides along with whatever ships next — no dedicated release needed.
🤖 Generated with Claude Code
https://claude.ai/code/session_016A7nD9KjjwujFHr17SBybh