SparkGlim LogoSparkGlim

White Label Coverage

Use this page as the implementation checklist for what the current white-label platform covers across ticketing, voting, fundraising, sync, and operations.

OverviewGetting StartedAuthenticationAPI ReferenceCoverageIntegrations

Tenant API Surface

Backend routes already implemented for creator-owned white-label tenants.

  • Campaign APIs: list, create, update
  • Ticketing APIs: ticket type list, create, update, verify, and check-in
  • Voting APIs: participant list, create, update, and vote payment initialization
  • Fundraising APIs: donation initialization and fundraising summary
  • Payments APIs: provider-routed payment initialization for ticketing, voting, donations, and branded channels
  • Notifications APIs: branded email and SMS dispatch through tenant providers
  • Withdrawals APIs: creator-linked withdrawal request creation
  • Settings APIs: merged settings read and per-category update
  • Analytics APIs: account metrics, revenue totals, and recent transaction visibility

Portal And Channel Coverage

Non-frontend operational flows implemented through the backend.

  • Creator portal context route for enabled tenants
  • Organizer portal route for account-scoped event operations
  • Vendor portal read route plus registration action updates
  • Nominee portal route for voting-side visibility
  • Webhook handlers for payment provider callbacks, notification provider callbacks, and third-party integration events
  • USSD white-label routing foundation with account and campaign mapping
  • Telegram commerce flows for ticketing, voting, fundraising, OTP handling, and verification
  • WhatsApp commerce flows for ticketing, voting, fundraising, OTP handling, and verification

Data Sync And Mirroring

Database structures and sync paths already defined in the white-label migration layer.

  • Dedicated domains, settings, provider configs, and API keys

Security And Admin Controls

Controls implemented to keep tenant access isolated and auditable.

  • HMAC-signed tenant API authentication with scoped API keys
  • Per-request API logging with request IDs, signature status, and latency
  • Reconciliation, export, monitoring, and account health checks
  • In-memory rate limiting and backend-only execution