Movie support

Segment types

Movies have two segments and are keyed by IMDb id alone. No season, no episode.

Reading

Pass is_movie=true to /segments. The response includes post_credits and media_type.

curl "https://api.introdb.app/segments?imdb_id=tt0371746&is_movie=true"

curl "https://api.introdb.app/outro?imdb_id=tt0371746"

Submitting

Set is_movie: true and drop season/episode. Works with a session, the submit form, or an API key. Say Iron Man's credits roll from 1:59:00 to 2:06:00 with the Nick Fury scene at 2:05:15:

{
  "imdb_id": "tt0371746",
  "is_movie": true,
  "segment_type": "outro",
  "start_sec": "1:59:00",
  "end_sec": "2:06:00"
}

{
  "imdb_id": "tt0371746",
  "is_movie": true,
  "segment_type": "post-credits",
  "start_sec": "2:05:15",
  "end_sec": "2:05:55"
}

End credits allow 5–900s, post-credits 5–600s. Aggregation works exactly like TV: matching submissions cluster, the strongest cluster goes live, outliers go to review.

Mid-credits scenes

Some scenes play after all the credits, others mid-credits with more credits after. The convention is the same:

• End credits end where the scene starts, or where the credits end if there is no scene.
• Post-credits covers just the scene, start to finish. Never the final frame.
• Credits after the scene aren't modeled; players seek to the end once the scene finishes.

TV vs movies