canonical: https://jentic.com/apis/kissashuru.com/kissashuru # Kissa Shuru The Kissa Shuru API serves the movie library and device network behind the Kissa Shuru offline viewing service. Mobile operations list movies page by page, return movie details and dashboard data for a user profile, and issue a download OTP for a video, while partner operations log a partner in, list their assigned customers, customer credits, and devices, assign offline download tasks to a device, and record device returns. Location lookups return states, districts, talukas, and villages. ## For AI agents List Kissa Shuru movies and their details, check a movie's availability for a partner, assign offline download tasks to devices, and look up partner customers, credits, and locations. ## Scope Does not stream video online, transcode files, or process card payments. Use for Kissa Shuru movie listings, partner customers, and device download tasks only. ## Capabilities - List movies page by page with per_page and page, and read a movie's details by movie_id for a user profile - Assign an offline download task to a device for a customer, with entertainment_id, priority, and size_bytes - List the customers assigned to a partner and their credit balances - List a partner's devices and record a device returned to the partner with deviceId and userId - Request a download OTP for a video by videoId - Look up states, districts, talukas, and villages for location selection ## Use cases ### AI agent partner operations through Jentic A distribution partner's agent handles routine device work: it searches Jentic for 'assign a download to a device', loads the Kissa Shuru download task operation with its input schema, and queues a movie for a customer's device. Your own Jentic One instance injects the partner bearer token at call time, so the agent never holds it. Example prompt: Call POST `/api/device-download-tasks/assign` with customer_id 8, device_id 5, entertainment_id 12, partner_id 3, offline_download 1, priority 2, and size_bytes 1048576 ### Partner customer and credit review A partner reviews who they serve and how much credit each customer has left. GET `/api/customers` lists the customers assigned to the partner, GET `/api/customers/credits` returns their credits, and GET `/api/device-partners/list` shows the devices in the partner's care. Example prompt: Call GET `/api/customers` and GET `/api/customers/credits`, then list customers with credits alongside GET `/api/device-partners/list` ### Movie browsing in a mobile app A mobile client lists movies page by page, optionally filtering restricted titles with is_restricted, then opens a movie's details for the current user and profile. Dashboard operations return the home screen data for that profile. Example prompt: Call GET `/api/v2/movie-list` with per_page 30 and page 1, then GET `/api/v2/movie-details` with a movie_id, user_id, and profile_id from the results ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v2/movie-list` | List movies | | GET | `/api/v2/movie-details` | Get movie details | | POST | `/api/device-download-tasks/assign` | Assign a download task to a device | | GET | `/api/customers` | List customers assigned to the partner | | GET | `/api/customers/credits` | List customer credits | | POST | `/api/partners/return-device` | Return a device to the partner | | POST | `/api/get-download-otp` | Get a download OTP for a video | ## Key resources - **Movies and dashboard** — Movie list, movie details, expiry details, pay-per-view list, and dashboard data for a user profile - **Partners** — Partner login, partner list, device list, device returns, movie availability, and download task assignment - **Customers** — Customers assigned to a partner, their credits, and lookup by mobile - **Locations** — States, districts, talukas, and villages ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 74 / 100 - AI-Readiness & Agent Experience: 41 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/kissashuru.com/kissashuru/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Kissa Shuru by hand means logging a partner in for a bearer token, knowing which operations need it and which are open, and shaping download task bodies yourself. Through Jentic you install once, import Kissa Shuru from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Kissa Shuru passes its customer, device, and movie targets in query parameters or the request body, so limit the agent to the operations it needs, such as listing movies and partner customers. Rules bound which operations your agent may call, not which customer, so download assignment or device returns are not included unless you add them. - **Credential handling:** Your Kissa Shuru token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list movies' or 'assign a download to a device', and Jentic returns the matching Kissa Shuru operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **The Movie Database API** — Public movie metadata, images, and credits - **Vimeo API** — Video hosting and distribution platform ## FAQ ### What authentication does the Kissa Shuru API use? Per its OpenAPI spec, the Kissa Shuru API uses a bearer token, required on partner operations such as GET `/api/customers` and POST `/api/device-download-tasks/assign.` Many mobile and lookup operations, including the movie list, movie details, partner login, and location lookups, are marked as open. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time. ### Can I assign a movie download to a device with the Kissa Shuru API? Yes. POST `/api/device-download-tasks/assign` takes customer_id, device_id, entertainment_id, partner_id, offline_download, priority, and size_bytes in the request body and queues the download for that device. ### What are the rate limits for the Kissa Shuru API? The OpenAPI spec does not specify rate limits. Check with Kissa Shuru at https://kissashuru.com for current limits. ### Is there a Kissa Shuru MCP server? You don't need an MCP server to give your agent the Kissa Shuru API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the movie and partner operations on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Kissa Shuru API? Yes. For example, write a rule that allows only GET `/api/customers`, GET `/api/customers/credits`, and GET `/api/device-partners/list`, so the agent can review customers, credits, and devices but cannot assign downloads or record device returns. Every call it makes through your instance is logged. ### How do I list Kissa Shuru movies through Jentic? Search Jentic for 'list Kissa Shuru movies', load the movie list operation, and call GET `/api/v2/movie-list` with per_page and page. To run it on your own infrastructure, install Jentic One from its GitHub repo.