Overview

The SuperApp SDK enables web developers to build MiniApps that run within the Grab SuperApp WebView. It provides a type-safe bridge for communication between web applications and native Android/iOS capabilities.

Each module encapsulates a specific domain of functionality, offering strongly-typed APIs with consistent response patterns.

Key Features

• Type-Safe APIs — Full TypeScript support with comprehensive type definitions
• Modular Architecture — Import only the modules you need
• Consistent Response Pattern — All methods return standardized bridge responses with HTTP-style status codes
• Streaming Support — Real-time data streams for location updates and media events
• Automatic Fallbacks — Graceful degradation when native features are unavailable

Installation

NPM (ES Modules)

npm install @grabjs/superapp-sdk

import { ContainerModule, LocationModule } from '@grabjs/superapp-sdk';

CDN (UMD Bundle)

<script src="https://cdn.jsdelivr.net/npm/@grabjs/superapp-sdk/dist/index.js"></script>
<script>
  const { ContainerModule, LocationModule } = window.SuperAppSDK;
</script>

Usage

Basic Module Initialization

All modules are instantiated with a simple constructor call:

import { ContainerModule, LocationModule, IdentityModule } from '@grabjs/superapp-sdk';

// Initialize modules
const container = new ContainerModule();
const location = new LocationModule();
const identity = new IdentityModule();

Handling Responses

All SDK methods return a standardized response with HTTP-style status codes:

import { CameraModule } from '@grabjs/superapp-sdk';

const camera = new CameraModule();
const response = await camera.scanQRCode({ title: 'Scan Payment QR' });

switch (response.status_code) {
  case 200:
    // Successfully scanned - result contains the QR code data
    console.log('QR Code scanned:', response.result.qrCode);
    break;
  case 204:
    // User cancelled the scanning operation
    console.log('Scanning cancelled');
    break;
  case 400:
    // Bad request - invalid request parameters
    console.error('Invalid request:', response.error);
    break;
  case 403:
    // Camera permission not granted to the Grab app
    console.error('Camera permission denied:', response.error);
    break;
  case 501:
    // Not implemented - not running in Grab app
    console.error('Requires Grab SuperApp environment');
    break;
  default:
    console.error('Unexpected error:', response);
}

Working with Streams

Some modules provide streaming methods for real-time data:

import { LocationModule } from '@grabjs/superapp-sdk';

const location = new LocationModule();

// Subscribe to location updates
const stream = location.observeLocationChange();

const subscription = stream.subscribe({
  next: (response) => {
    if (response.status_code === 200) {
      console.log('Location:', response.result);
    }
  },
  complete: () => {
    console.log('Stream ended');
  },
});

// Unsubscribe when done
subscription.unsubscribe();

Available Modules

• ContainerModule — Control the WebView container UI and lifecycle (header, loading indicators, analytics, connection verification)

• IdentityModule — Authenticate users via GrabID OAuth2/OIDC with PKCE support

• LocationModule — Access device location services and subscribe to location updates

• StorageModule — Persist key-value data locally with type-safe storage

• CameraModule — Access device camera capabilities for QR code scanning

• CheckoutModule — Trigger native checkout flows for payment processing

• DeviceCapabilityModule — Query device hardware capabilities

• FileModule — Handle file operations including downloading from remote URLs

• LocaleModule — Access device locale and localization settings

• MediaModule — Handle media playback including DRM-protected content

• PlatformModule — Access platform information and navigation controls

• ProfileModule — Access user profile information including email

• ScopeModule — Manage permission scopes from GrabID

• SystemWebViewKitModule — Handle system WebView operations and external browser redirections

• UserAttributesModule — Access user attribute data

Important: Always call ScopeModule.reloadScopes() after an OAuth redirect to load the latest permissions from GrabID. Without this, module methods may return 403 errors even when permissions have been granted.

Response Status Codes

The SDK uses HTTP-style status codes for all responses:

Code	Type	Description
200	OK	Request successful, result contains response data
204	No Content	Request successful, no data returned
302	Redirect	OAuth redirect in progress
400	Bad Request	Invalid request parameters
401	Unauthorized	Authentication required
403	Forbidden	Insufficient permissions for this operation
404	Not Found	Resource not found
424	Failed Dependency	Underlying native request failed
426	Upgrade Required	Requires newer Grab app version
500	Internal Error	Unexpected SDK error
501	Not Implemented	Method requires Grab SuperApp environment

Type Guards

The SDK provides type guards for response validation:

import { isSuccess, isErrorResponse, isClientError, isServerError } from '@grabjs/superapp-sdk';

const response = await someModule.someMethod();

if (isSuccess(response)) {
  // TypeScript knows response.result is available
  console.log(response.result);
}

if (isErrorResponse(response)) {
  // TypeScript knows response.error is available
  console.error(response.error);
}

Best Practices

2. Handle all status codes in your switch statements, including unexpected ones.

3. Use type guards for cleaner response handling and better type inference.

4. Call reloadScopes() when your MiniApp launches and after OAuth before accessing protected resources.

5. Unsubscribe from streams when your component unmounts or you no longer need updates.