Identity & Auth APIs
Login, token issue, verification checklist, email confirmation, profile settings.
Developers
Build, test, and scale integrations on top of Spherenet OS with production-ready APIs and developer tooling.
Last updated: 27 March 2026
Overview
Spherenet gives teams one platform for identity, workspace modules, messaging, and admin workflows. Use this page as your starting point for integration architecture, test tooling, and go-to-market API products.
- Secure API access with bearer tokens and session-aware routing.
- Modular app model for dashboard windows, messaging, learning, and marketplace features.
- Developer-first lifecycle: design → test data generation → automation checks → production rollout.
API Platform
Use REST endpoints for account, workspace, app assignments, and operational flows. Typical usage pattern:
- Authenticate and issue/attach bearer token.
- Call feature endpoint (for example app marketplace, org setup, profile settings, notifications).
- Validate response and update module UI state.
- Track usage + errors for billing and support SLAs.
Workspace & Module APIs
Bootstrap data, app assignment, app marketplace, dashboard summaries, user modules.
Org Setup APIs
Create organisation, invite admins, add users, save onboarding steps, finalize setup.
Sellable API Ideas
KYC / Verification API
Expose identity checks, email confirmation status, and compliance-ready verification scoring.
Org Onboarding API
Offer create-organisation, invite-admin, add-users as a packaged onboarding product for B2B apps.
App Marketplace API
Monetize app catalog discovery, assignment workflows, usage metering, and provisioning events.
Notifications API
Paid delivery + read-state analytics for internal products and partner systems.
Dev Tools: Development
- API Explorer: token-aware endpoint runner with response schema previews.
- SDK Starters: quick bootstrap templates (PHP, JS, Node) for auth + route wiring.
- Webhook Inspector: replay and verify callback payloads during development.
- Environment Switcher: local/stage/prod config profiles with one-click endpoint switching.
Dev Tools: Testing
Provide purpose-built generators so teams can test banking-style and enterprise workflows quickly and safely.
Data Generator: IDs
LiveGenerate realistic personal/company ID patterns with rule-based regional formats.
Scope: test.ids.generate
Rate: 60/min
Example input/output
{
"region": "ZA",
"kind": "person",
"count": 2
}Data Generator: Virtual Cards
BetaProduce test card profiles (never real cards) with expiry, limits, and status transitions.
Scope: test.cards.generate
Rate: 30/min
Example input/output
{
"brand": "visa",
"currency": "ZAR",
"status": "active"
}Data Generator: People Profiles
LiveSeed banker/client/operator profiles for multi-role testing across systems.
Scope: test.profiles.generate
Rate: 50/min
Example input/output
{
"persona": "operator",
"locale": "en-ZA",
"count": 3
}Scenario Packs
LivePrebuilt journeys: onboarding, KYC pending, approved, declined, and support escalations.
Scope: test.scenarios.run
Duration: 2–6 min
Example scenario payload
{
"scenario": "kyc-pending-to-approved",
"notify": true,
"assertions": ["status", "timeline"]
}Validation Checklist
LiveQuick API quality gate before release: schema, auth scope, rate-limit and error contract checks.
Scope: test.validation.read
CI-ready
- Bearer token present + scope check
- Response schema + examples valid
- Retry + 4xx/5xx behavior asserted
Dev Tools: Site Crawlers
- Click-Flow Crawler: visits key pages, performs scripted clicks, and flags broken journeys.
- Form Crawler: validates required fields, button states, and submit responses.
- Auth Journey Crawler: checks login, OTP, verify, and logout flow stability.
- Release Gate Report: exports pass/fail results for CI deployment checks.
Trust & Status
- Status page: status.spherenet.co.za
- Security baseline: token-based access, least-privilege roles, and endpoint-level access control.
- Data handling: test generators produce synthetic data only and are intended for non-production use.
- Support SLA: incident acknowledgment and update cadence are published through support and status channels.
Quick Start
- Request developer access and API credentials.
- Pick your target integration (identity, org setup, marketplace, notifications).
- Use test data generators and crawler checks before production rollout.