Deep link integration

How it works

The public base URL is https://app.gbc.my. Prefer HTTPS links for sharing: they provide a web fallback when the app cannot open. For an explicit “Open in e-Sabda” action, use the custom scheme my.gbc.app:// with the same route.

https://app.gbc.my/bible/Kejadian/1/1
my.gbc.app://bible/Kejadian/1/1

These links navigate inside the app. They do not return Bible text, grant a content license, or provide a verse API.

Supported routes

Parameters and content

Use a book name from the complete reference below, preserving its spelling, capitalization, spaces, and hyphens. Encode each path segment individually; for example, 1 Yohanes becomes 1%20Yohanes. Use positive integer chapter, verse, and footnote numbers that exist in the referenced book. For hymns, use the number formats and examples below, including any letter prefix.

The route prefixes bible and kidung are lowercase. Use the documented lowercase outline and fn segments. Verse ranges, multiple references, cross-reference routes, and language-selection parameters are not supported by this interface.

If an outline is unavailable, the app opens chapter 1. If a footnote is missing, it reports that and opens the parent verse. Invalid books, chapters, verses, or hymns lead to the corresponding content home screen with an alert. Missing licensed content prompts the reader to obtain access. Links may wait while content loads.

Valid Bible book names

These are all 66 valid book names for the Bible bundled with e-Sabda. Use the exact name or its encoded URL segment below. Abbreviations and alternate spellings are not accepted by the deep link route.

Names such as Pengkhutbah, Kisah Para Dutus, and Wahi follow this edition’s spelling.

Kidung numbers and prefixes

A hymn number is a text identifier, so keep any letter prefix. Use uppercase A and T, with no space or leading zeros: A1 and T1, rather than a1, A 1, or T01.

https://app.gbc.my/kidung/A1
https://app.gbc.my/kidung/T114
my.gbc.app://kidung/A1
my.gbc.app://kidung/T114

The reader needs the hymn content installed and accessible in e-Sabda.

Build a link

This builder creates a verse URL. The reference must exist in the reader’s installed Bible.

https://app.gbc.my/bible/Kejadian/1/1

Build a Kidung link

Choose a number format and hymn number to create a shareable link.

https://app.gbc.my/kidung/5

Integration examples

Website

<a href="https://app.gbc.my/bible/Kejadian/1/1">
  Read Kejadian 1:1 in e-Sabda
</a>

JavaScript / React Native

const book = encodeURIComponent('1 Yohanes');
const url = `https://app.gbc.my/bible/${book}/1/1`;

// React Native: import { Linking } from 'react-native';
await Linking.openURL(url);

iOS (Swift)

let url = URL(string:
    "https://app.gbc.my/bible/Kejadian/1/1")!
UIApplication.shared.open(url)

Android (Kotlin)

val url = Uri.parse(
    "https://app.gbc.my/bible/Kejadian/1/1")
startActivity(Intent(Intent.ACTION_VIEW, url))

Open links as external navigation from a user action. Embedded webviews and browser preferences can keep an HTTPS link in the browser. A custom-scheme link requires an installed handler; handle a failed open and offer the app store links. Avoid automatic redirect loops or assuming installation from a timer.

Test your integration

1. Install a build with deeplink support and set up the relevant licensed content.
2. Tap an HTTPS reference from another app and verify the expected destination.
3. Test the app both closed and already running, plus missing content and invalid references.
4. Test without the app installed: the HTTPS URL should show the download landing page.