Skip to main content
This guide walks you through building a minimal app on top of the Jumper Public API: a search box, a submit action, and a results list with thumbnails. That is enough to prove the setup works.
Before you begin: Jumper is running with media analyzed, you have a Jumper Pro license, and you know the path to your analysis folder.
You do not need to write the code yourself. Paste the starter prompt below into a coding agent (Cursor, Codex, Claude Code, or similar) and follow its instructions.

​
Starter prompt

Copy this into your coding agent: 
Build a very small local app that connects to the Jumper API.

Goal:
1) Show a search input box
2) Send the query to Jumper
3) Render results as a simple list with thumbnails and clip info

When done, tell me exactly how to test it.

Assume that I have Jumper Pro running and my footage is already analyzed.

Use this API reference: https://docs.getjumper.io/api-reference

​
Optional: specify a tech stack

If you have a preference, say so in the prompt. Many agents default to JavaScript. 
Use JavaScript with React, shadcn components, and Tailwind for styling.
Other stacks work too, including a CLI in Python, a desktop app, or a plain HTML page. The Jumper API does not care what language or framework you use.

​
What the agent will ask for

When testing, the agent or app will usually need:
  • Your Jumper Pro license key
  • The path to your analysis folder (the cache_dir in API requests)
Point the agent at the OpenAPI spec if it needs endpoint schemas or request fields.

​
Test it

1

Keep Jumper running

The API is local. Your app talks to Jumper on your machine at http://localhost:6699/api/v1.
2

Run the app

Follow the instructions the agent gives you. If you are unsure, ask it: “How do I test the app?” or “Can you start the app for me?”
3

Run a search

Enter a query you know should return results from your analyzed footage. Confirm you get thumbnails and clip info back.
4

Verify the basics

Check that results match media you have analyzed in Jumper. Try a second query to confirm the connection is stable.

​
If something breaks

Paste the error message back to the agent and ask it to fix the issue. That is usually faster than debugging it yourself.
  • Confirm Jumper is running
  • Confirm the footage has been analyzed
  • Check the analysis folder path matches the one in Settings
  • Confirm the media_paths in the request point at analyzed files
  • Confirm Jumper is running
  • Confirm the base URL is http://localhost:6699/api/v1
  • Try GET /health with curl. See API reference
  • Confirm you have a Jumper Pro license
  • Check the license key is correct
  • Send the key in the X-License-Key header or in the request body as license_key

​
What’s next

Once search works, add features one at a time instead of trying to build everything at once. Common next steps:
  • Switch from a list to a card or deck view for review
  • Add keyboard shortcuts for faster selects
  • Save favorites and batch-export them as clips
  • Drag a result to Finder or Explorer to export a trimmed clip
  • Combine Jumper results with another API or tool you already use
For inspiration on iterating from a basic search UI to more elaborate review tools, see Vibe-Coding Your Own Video Editing Tools on the Jumper blog.

Developers overview

What Jumper handles, who this is for, and how the pieces fit together

API reference

Authentication, workflow, endpoint groups, and curl examples

Agentic editing

Use an AI agent to operate Jumper directly instead of building your own app
Last modified on June 22, 2026