Jetstream Launch

Jetstream Launch is a public, read-only GraphQL Content API. It turns a curated collection of Hope Channel content - a property - into the data that backs a standalone application: a web site, a mobile app, or a TV app. One property can power many applications, and the same API serves web, mobile, and TV clients from a single content set.

This is the integration reference for developers building those clients. You do not need any Hope.Cloud backend knowledge - point a client at the endpoint, send your app key, and read content.

What you get

Given a property id, the API returns the property's curated brands, their seasons and episodes (each with a ready-to-play HLS URL and a transcode status), and its curated live streams. The service is read-only - there are no mutations.

Endpoints

Environment	GraphQL endpoint
dev	https://launch-dev.jetstream.studio/graphql
stage	https://launch-stage.jetstream.studio/graphql
prod	https://launch.jetstream.studio/graphql

GET /health (no key) returns {"status":"ok"}.

Introspection is open. Point any GraphQL client (the Apollo landing page at the endpoint URL, Apollo Sandbox, Insomnia, ...) at the endpoint to explore the live schema. Introspection needs no app key.

Start on dev

dev is the first environment made available to integrators and mirrors the production contract. Build against it first.

Documentation

• Authentication - the X-App-Key header and how to get a key.
• Queries - runnable example queries to fetch a property and its content.
• Types - the full object and enum reference.
• Playback & images - how playbackUrl and coverUrl behave.
• Errors - the extensions.code values to branch on.
• Versioning & stability - how the schema evolves and what clients must tolerate.

30-second quickstart

1. Get an app key (prk_…) from the Hope.Cloud team.
2. Send it in the X-App-Key header to the endpoint:

curl -s https://launch-dev.jetstream.studio/graphql \
  -H 'content-type: application/json' \
  -H 'X-App-Key: prk_your_key_here' \
  -d '{"query":"{ property(id:\"<your-property-id>\"){ name } }"}'

3. Then walk the content tree - see Queries.