A tiny sample app that shows what it takes to put Launch Pad path planning inside your own product. It plays a fictional partner, "Your Ag App", makes real calls to the Launch Pad public REST API, and shows every request and response in a live log. Click through it with your own API key, then read the source.
Runs in your browser, nothing to install. You need a Launch Pad API key with the Partner Admin flag; contact Verge Ag API support to get it.
Partners add Launch Pad path planning to their product without building path planning themselves, and their users never upload a boundary file or create an account. This demo exists so your developers can see that whole integration end to end, with real API traffic, before writing a line of code. Scoping it takes about ten minutes.
Your backend authenticates as your Partner Admin service account: one
privileged API key, sent as
X-API-KEY on every request.
Your users never have keys.
As that account, create everything before your user arrives: the user, their company/organization, and their access, then the land - company/organization > grower > farm > field > boundary (CGFFB). No account creation and no boundary upload for your users, ever.
Request a single-use launch code and open Launch Pad signed in as your user: the person using your app, the one step 2 provisioned. They land straight on that boundary. No sign-up, no login screen, no import.
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.
The same handoff, but Launch Pad renders inside your own UI in an iframe, with its navigation hidden and a partner theme applied.