Overview
By default, the Bluvo SDK sends requests toapi-bluvo.com. The customDomain option lets you route traffic through your own domain instead (e.g., bluvo.my-company.com). Common reasons to do this:
- Branding — keep all API traffic under your own domain
- Compliance — satisfy internal policies that require first-party endpoints
- Proxy control — route through your own infrastructure for logging or access control
DNS Setup
Create CNAME records pointing your subdomain to Bluvo’s servers.| Environment | Your Record | Points To |
|---|---|---|
| Production | bluvo.my-company.com | api-bluvo.com |
| Test / Sandbox | test-bluvo.my-company.com | test.api-bluvo.com |
CORS Configuration
No extra CORS setup is needed on your side. Bluvo’s API accepts requests from CNAME’d origins automatically.SDK Configuration
ThecustomDomain option in BluvoFlowClientOptions accepts three forms:
| Form | Type | Behavior |
|---|---|---|
| Single string | string | Used for both API and WebSocket connections |
| Default literal | "api-bluvo.com" | No override — equivalent to omitting the option |
| Separate endpoints | { api: string, ws: string } | Different domains for API calls and WebSocket connections |
Usage Example
Next Steps
State Machine Reference
Full list of states, transitions, hook booleans, and context data
Error Handling & 2FA
Error recovery patterns and exchange-specific 2FA behavior
Encryption & Security
How Bluvo encrypts and isolates exchange credentials
Code Samples
Full working examples for Next.js, React, and more