Resolve Video Moments Api
GET/v2/videos/{video_id}/moments/resolve
Follow moment ids from an earlier computation to the latest stored moments.
Same authorization as other video GETs (owner, admin, shared, or sample). This call does not start a computation. It answers from the latest stored moments even when those are stale.
moments_status and stale mean the same thing as on
GET /v2/videos/{video_id}/moments. generation and profile_version
identify that stored computation, together with computed_at: generation
and profile_version can stay the same across a recomputation, and
computed_at changes whenever the stored moments do.
Each results row echoes the id that was asked:
current— the id is in the latest stored moments.current_idis that id.superseded— the id was followed to an id in the latest stored moments. That is the best overlapping moment for the same subject and kind, which can be a moment that also absorbed a neighbor. Check the span before treating it as the same event. A moment tied to a stimulus is followed only to a moment for that same stimulus.gone— nothing for the same subject and kind overlapped enough.current_idis null. This is not proof the event ceased to exist: a subject change, for example, has no eligible overlap.unknown— the id is in neither the latest stored moments nor a computation this answer can follow.current_idis null. Ids from older computations may be reported as unknown.
Request
Responses
- 200
- 422
Successful Response
ids is missing, empty, longer than 200, or an id is longer than 256 characters. The check runs after the video is authorized. The body is {"detail": "<message>"}.