Skip to content

fix: use correct Amplitude vardata path#88

Merged
angeloashmore merged 1 commit into
mainfrom
aa/fix-amplitude-vardata-path
Apr 8, 2026
Merged

fix: use correct Amplitude vardata path#88
angeloashmore merged 1 commit into
mainfrom
aa/fix-amplitude-vardata-path

Conversation

@angeloashmore
Copy link
Copy Markdown
Member

@angeloashmore angeloashmore commented Apr 8, 2026

Resolves:

Description

The Prismic Amplitude proxy serves the Experiment SDK under /api, so requests to /sdk/v2/vardata return 404. Add the missing api/ prefix so flag evaluation matches the path the editor uses.

Checklist

  • A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
  • If my changes require tests, I added them.
  • If my changes affect backward compatibility, it has been discussed.
  • If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA

Run npx prismic sync from a repository without Type Builder access — it should no longer fail with Amplitude flag evaluation failed: 404.


Note

Low Risk
Low risk one-line URL change; main risk is if any environment expects the previous non-/api Amplitude proxy path, which could break flag evaluation.

Overview
Updates Amplitude Experiment flag evaluation to call the correct vardata endpoint by adding the missing /api prefix (sdk/v2/vardataapi/sdk/v2/vardata), preventing 404s when fetching flag values via the proxy.

Reviewed by Cursor Bugbot for commit 93d7b48. Bugbot is set up for automated code reviews on this repo. Configure here.

The Prismic Amplitude proxy serves the Experiment SDK under `/api`, so
requests to `/sdk/v2/vardata` 404. Add the missing `api/` prefix to
match the proxy layout used by the editor.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@angeloashmore angeloashmore merged commit e7aa64c into main Apr 8, 2026
13 checks passed
@angeloashmore angeloashmore deleted the aa/fix-amplitude-vardata-path branch April 8, 2026 05:04
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