Division Integration Guide
Connect your division apps to the SphereUs Nation network for unified authentication, shared services, and cross-division features.
📋 Get Copy-Paste Integration TemplateArchitecture Overview
Each division remains a separate app with specialized features. SphereUs.com serves as the central authentication and data hub.
Federated Network Benefits:
- Each division keeps specialized features and independence
- Single Sign-On across all divisions
- Shared user profiles and SU Coin balances
- Unified marketplace and dashboard
- Automatic Foundation contributions (5%)
Single Sign-On (SSO) Integration
Authentication Flow:
Example: user goes to guidedaim.com
window.location.href = 'https://sphereus.com/auth/login?redirect=https://guidedaim.com/callback'User logs in once, credentials managed centrally
https://guidedaim.com/callback?token=eyJhbGc...Verify token with SphereUs API, establish session
Implementation Note:
Base44 provides built-in authentication. Each division app can use the same Base44 authentication system, or implement OAuth2-style token exchange for custom setups.
Shared Services API
Division apps can access shared SphereUs data through API calls:
Get User Profile
GET https://sphereus.com/api/user/:userIdReturns: user profile, SU Coin balance, wallet address
Report Transaction (for SU Coins)
POST https://sphereus.com/api/transactions
{ "user_id": "...", "amount": 100, "type": "purchase", "division": "Guided Aim" }Automatically awards SU Coins and tracks Foundation contribution
Create Marketplace Listing
POST https://sphereus.com/api/listings
{ "title": "...", "division": "Guided Aim", "price": 50, ... }Listings appear in unified SphereUs Marketplace
Check SU Coin Balance
GET https://sphereus.com/api/coins/:userIdReal-time SU Coin balance for display in division apps
Optional: SphereUs Widget
Embed a widget in your division app to show SphereUs features:
Widget Features:
- • Display user's SU Coin balance
- • Quick link to SphereUs Dashboard
- • Link to Marketplace
- • Show other division quick links
<!-- Embed in your division app -->
<iframe
src="https://sphereus.com/widget?userId={userId}"
width="300"
height="200"
style="border: none; border-radius: 12px;"
></iframe>User Verification Requirements
SphereUs uses tiered verification to ensure trust and safety across all divisions.
Phase 1: Phone Verification
Required for: Service providers, especially BudVan drivers and home services
- • Check:
user.phone_verified === true - • Redirect users to:
https://wirks.com/verification
Phase 2: Identity Verification
Required for: Receiving payments, BudVan drivers, high-value transactions
- • Check:
user.verification_tier === 'verified' - • Uses Stripe Identity (~$1.50/check)
- • Photo ID + selfie verification
Example Implementation:
// Before allowing service listing
if (!user.phone_verified) {
alert('Please verify your phone number first');
window.location.href = 'https://wirks.com/verification';
return;
}
// Before processing payments to user
if (user.verification_tier !== 'verified') {
alert('ID verification required to receive payments');
window.location.href = 'https://wirks.com/verification';
return;
}Implementation Checklist
Need Integration Help?
Our technical team can assist with setting up SSO and API integration for your division.
Contact Technical Support