Skip to main content

Getting Started

Integrate Vespid's financial literacy platform into your application.

Integration Methods

MethodDescriptionBest For
BrowserLink users to Vespid web appQuick setup, mobile browsers
EmbeddedWebView/iframe in your appSeamless in-app experience

Authentication Modes

Auth ModeDescriptionRequires API Key
NativeUsers login/register on VespidNo
APIYour backend authenticates usersYes

Compatibility

IntegrationNative AuthAPI Auth
Browser
Embedded

Quick Start

Browser + Native Auth (Simplest)

Link users to Vespid with your partner param:

https://integration.vespid.my?partner=<partner_registration_code>

Learn more →

Embedded + API Auth (Seamless)

  1. Your backend calls SSO API
  2. Pass token to WebView
  3. Users are automatically logged in

Learn more →

Prerequisites

RequirementNative AuthAPI Auth
Partner registration param
API Key from Vespid

Environments

Vespid provides two environments for partner integration.

EnvironmentWeb AppAPI BaseAPI Key Prefix
Staginghttps://staging-integration.vespid.myhttps://api-staging.vespid.myvspd_test_*
Productionhttps://integration.vespid.myhttps://api.vespid.myvspd_live_*
tip

All code examples in these docs use production URLs for clarity. When integrating, point your implementation at the staging URLs first and only switch to production after your integration is verified.

Onboarding Flow

Vespid follows a staging-first onboarding model. Production access is granted only after your integration is verified on staging.

  1. Receive staging credentials. Your Vespid account manager issues a staging Partner Registration Code and (for API Auth) a staging API key (vspd_test_*).
  2. Build against staging. Implement your integration using the staging URLs from the Environments table.
  3. Self-test. Verify the full user flow (login/SSO, partner association, learning experience) end-to-end on staging using synthetic test users.
  4. Joint review. Walk through the integration with your Vespid account manager. We confirm requests are arriving correctly and your partner association is recorded.
  5. Receive production credentials. After sign-off, you'll be issued a production Partner Registration Code and API key (vspd_live_*).
  6. Production smoke test. Swap the staging URLs and credentials for production and run one or two calls against a designated test account before exposing the integration to real users.
  7. Go live.
Staging guardrails

Staging data is non-production and may be reset without notice. Always use synthetic test users — never real customer emails — while integrating. Staging is rate-limited; contact us before running load tests.

Next Steps