Remove hardcoded /api/v2/ prefixes from backend URLs (follow-up to #6938)
#7046
+9
β14
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.



What type of PR is this? (check all applicable)
Describe this PR
This PR cleans up redundant
/api/v2/prefixes across API endpoints, following up on #6938contributed by @jake-low.
Background
In #6938, @jake-low removed hardcoded
/api/v2prefixes to support non-standard backend URLs. While that PR fixed the main issue, there were additional occurrences of/api/v2/prefixes across the codebase. This PR rebases and extends their work, applying the cleanup consistently.Technical Note
The
URLconstructor merges relative paths with the base URL automatically:Even when both the base and relative path include
/api/v1/, the final URL is correct.This ensures that removing the redundant prefixes is safe, and no changes to
fetchLocalJSONAPI()were required.Changes
/api/v2/prefixes across the codebase.Outcome