List Sume's video endpoints from the OpenAPI JSON in Python
Pull the OpenAPI snapshot, print every /v1/videos and Video Router operation, and know which copy is the source of truth. A short Python script.

Sume publishes its API as an OpenAPI 3 JSON file, and the video endpoints are in it. A short Python script lists every /v1/videos and /v1/video-router operation so you can generate a client or diff against last week. The docs snapshot is at https://docs.sume.com/api/openapi.json; the live schema on the API service is the source of truth.
Which copy of the schema should you use?
The API reference says the markdown tables can be older than the live document, and names two places to read the schema: the local docs snapshot at /api/openapi.json and the live schema at https://api.sume.com/reference/json. Use the snapshot for a quick look and the live schema to generate code you will ship.
What does the script print?
It opens the snapshot and prints each operation whose path starts with the video prefixes.
import json, urllib.request
spec = json.load(urllib.request.urlopen("https://docs.sume.com/api/openapi.json", timeout=30))
for path, ops in spec["paths"].items():
if path.startswith(("/v1/videos", "/v1/video-router")):
for method, op in ops.items():
print(method.upper(), path, "-", op.get("summary"))What operations come back?
The snapshot lists these video operations.
| Method | Path | Summary |
|---|---|---|
| GET | /v1/videos/models | List video generation models |
| POST | /v1/videos | Submit a video generation request |
| GET | /v1/videos/{id} | Poll a video generation job |
| GET | /v1/videos/{id}/content | Download a generated video |
| GET | /v1/video-router/models | List Video Router models |
| GET | /v1/video-router/models/{model_id} | Get Video Router model |
| POST | /v1/video-router/generate | Generate via Video Router |
What do you do with the list?
Feed the live schema to your generator of choice, then still call GET /v1/videos/models at run time. The schema describes the request shape; the model list says which ids, durations and reference types are open today. The video generation docs recommend /v1/videos for new integrations.
Related posts
More in Developers
- List Sume video model limits with curl, jq and column in one table
curl GET /v1/videos/models into jq and column to see each model's duration range, resolutions and audio flag in one table. Documented limits for six models.
- List Sume video models: /v1/videos/models for limits, /v1/catalog
Two discovery routes, two jobs. /v1/videos/models returns durations, resolutions, aspect ratios and audio flags; the public /v1/catalog lists the wider catalog.
- LTX-2.5 on Windows or Mac: natten, attention and fallbacks
LTX-2's README: natten (VAE decode) is Linux and CUDA only, with a Triton or eager fallback elsewhere; FlashAttention 4 on B200, 3 on Hopper, SDPA otherwise.
- LTX-2.5 pipelines: Distilled, DFR or two-stage, which to run
The LTX-2 repo names eleven pipelines for LTX-2.5. Which one is fastest, which is guided, which does keyframes or audio, and where the Sume fields line up.
Written by Sume