Launch Pad partner integration demo

This app plays the role of "Your Ag App" - a fictional partner product that adds Launch Pad path planning to its own software. It makes real calls to the Launch Pad public REST API and shows you every request and response in a live log, so you can see exactly what your integration needs to do before writing a line of code. The app is kept deliberately small so you can read the source and copy from it.

You plus Verge Ag: your farm management system combined with Verge Ag's path planning produces planned fields for your users. Y You your farm management system + Verge Ag the path planning expert = Planned fields ready in Launch Pad for your users

The whole journey is three steps

  1. Setup - your backend authenticates with your Partner Admin service account: the one privileged API key every call runs as. Your end users never see or hold keys.
  2. Provision - as that account, create everything your user needs before they ever arrive: their identity and access (user + company/organization), then the land - company/organization > grower > farm > field > boundary (CGFFB).
  3. Hand off - request a single-use launch code and open Launch Pad signed in as your user: the person currently clicking around your app, the same one step 2 just provisioned. Your service account only does the asking; the session that opens belongs to them. They land straight on the boundary you pushed, and the only choice left is where that happens: A. Companion mode (new browser window) or B. Embedded mode (iframe in your UI).

The three steps map one-to-one to the sequence diagram on How it works.

flowchart LR
    S["1. Setup
connect your Partner Admin key"] --> P["2. Provision
user + company/org + access,
then grower, farm, field + boundary"]
    P --> H["3. Handoff
launch code signs in
YOUR user, not your key"]
    H --> A["A. Companion mode
(new browser window)"]
    H --> B["B. Embedded mode
(iframe in your UI)"]
You need a Partner Admin API key. Creating companies/organizations and users requires the Partner Admin flag on your account, and only Verge Ag can set it - without it the journey stops at step 2 with a 403. Contact Verge Ag API support to get it.

Start the journey: connect your key

Where Launch Pad appears: A or B

ACompanion mode new browser window

Launch Pad opens in a new browser window next to your app, deep-linked straight to path planning for the boundary you pushed, already signed in as your user.

See companion mode

BEmbedded mode iframe in your UI

The same handoff, but Launch Pad renders inside your own UI in an iframe, with its navigation chrome hidden and a partner theme applied.

See embedded mode

Read the source - this app is your sample code

Clicking through the pages shows you the journey; the code shows you the implementation, and you are expected to open it. The whole app is a handful of small files with no framework and no build step, written to be copied from: what you read is exactly what runs, including the same calls you just watched in the live log.

Start with js/api.js - one function per REST endpoint, request and response shapes in the comments, the fetch plumbing kept at the bottom. When you build your own integration, lift that file first. How it works has the full technical explanation of the demo, including what every file is for.