Clarify that managed profiles are optional and document the browser origin allowlist - #1367
Merged
Merged
Conversation
Agents reading the docs inferred that a custom UI or API-driven onboarding requires managed profiles. State the standalone-profile alternative where that inference happens.
Browser integrations fail at the CORS preflight until Vortex adds their exact origin, and the docs never said how to get one added.
✅ Deploy Preview for vortexfi canceled.
|
✅ Deploy Preview for vrtx-dashboard canceled.
|
✅ Deploy Preview for vortex-sandbox ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
A coding agent building against the published docs concluded that Managed Profiles are a prerequisite for a custom UI and API-driven onboarding. They are not. This clarifies that branch and documents the browser origin allowlist, which the docs never mentioned at all.
Managed profiles are an opt-in branch
The docs supported both ownership models but never named the choice, and three places implied managed profiles were mandatory.
Each mention also carries the corridor fact that decides it: EUR flows are bound to a verified login email, so EUR is standalone-only.
Browser origin allowlist
Browser integrations fail at the CORS preflight until Vortex adds their exact origin to the allowlist. The docs mentioned the internal
BROWSER_SDK_ORIGINSenv var in passing, which is not actionable for a partner, and never said how to get an origin added.New "Browser Origin Approval" section in Authentication And API Keys covers what it applies to (the SDK browser build, a
fetchfrom a partner front end,POST /v1/session/createcalled from page code; server-to-server unaffected), that entries are exact-match with wildcards never accepted, and that approval is requested by emailing support@vortexfinance.co with each exact origin and its environment. Pointers from Overview, Quick Start, AI Agent Integration section B, the Widget "when to use" table, and a Production Checklist item.Notes
bun run docs:api:checkpasses; theseoblocks inapidog/page-manifest.jsonwere updated for the two pages whose summaries changed.