Creator Zone

A. Creator Detail - Series (Seasons-based Episodes) Endpoint

• Status: Missing endpoint
• Need: A dedicated endpoint to fetch series data grouped by season and episode for Creator Detail.
• Expected response: series object with nested seasons[], and each season containing episodes[] with full metadata.

Client Response:

Creator Series (Seasons/Episodes) -> GET /tv/v3/creators/{id}/series: Returns paginated series with nested seasons[] (id, number, title), seasons_count, episodes_count, rating, and access tier badges.

Developer Observation:

I can see pagination values inside "data" object. Instead of it should be on "meta_data" on all endpoint which having the pagination must be followed the same structure.

Current JSON Response:

{
  "status": "success",
  "data": {
    "items": [...],
    "total": 7,
    "page": 1,
    "total_pages": 1
  }
}

Expected JSON Response:

{
  "status": "success",
  "meta_data": {
    "limit": 6,
    "total": 7,
    "page": 1,
    "total_pages": 1
  },
  "data": {
    "items": [...]
  }
}

• Status: Required endpoint / incomplete response
• Need: Show detail payload that includes full seasons and episodes data.
• Expected response: Full show metadata with seasons[] and nested episodes[].

Client Response: For full episode drill-down per series: GET /tv/v3/shows/{id} returns complete seasons[] → episodes[] with stream URLs and access gating.

Developer Observation:

Regarding the above point - I have passed the above series_id -> "id": "9bbbcf6a-bb81-4e03-8176-0ecf81877433", but I’m getting 500 Internal Server error.

curl -X 'GET' \
  'https://staging-api.drop.tv/tv/v3/shows/9bbbcf6a-bb81-4e03-8176-0ecf81877433' \
  -H 'accept: application/json'

JSON Response:

{
  "status": "error",
  "code": 500,
  "message": {
    "code": "INTERNAL",
    "message": "Internal server error"
  }
}

B. Creator Detail - Live Channel EPG Details and Schedule Missing

• Status: Missing data
• Need: EPG details and schedule data for the Creator Detail channel live UI.
• Expected response: Program listing per channel with start/end times, title, and description.

Client Response:

Two options depending on your use case:

GET /tv/v3/creators/{id} — Creator detail response includes channels[] with current_program + next_program (title, start/end time, thumbnail, duration) GET /tv/v3/guide/schedule — Full EPG schedule with ?channel_id=X, ?date=YYYY-MM-DD, and ?hours=N filtering

Developer Observation:

Right now I noticed all creators having “is_live”: false and “channels”: [] - so I can’t able to test “Channel LIVE” UI on Creator Detail Screen at the moment.

Developer Question:

Could you provide any of creators should have “is_live”: true and channel details - then I can check by calling new endpoint -> EPG schedule with filtering -> GET /tv/v3/guide/schedule?

C. Shows Segment - Show Detail Endpoint (Full Seasons and Episodes)

Client Response:

Show Detail (Full Seasons & Episodes) -> GET /tv/v3/shows/{id} Full show metadata with nested seasons[] → episodes[]. Each episode includes duration_formatted, thumbnail_url, stream_url, locked status, and gating_context for subscription-gated content.

Developer Observation:

Still I can see 500 Internal Server Error on Show Detail(Returns full show details including seasons and episodes)