影视聚合API

接口说明

影视聚合API提供影视资源的聚合搜索服务，支持按关键词检索并分页返回结果。适用于需要在应用或站点中集成影视查询功能的开发者。接口免费开放，无需申请密钥即可直接调用。

调用地址

接口的调用地址为：

http://shutiao.wsff.cn/apis/ncdx

请直接向该地址发起请求，地址已包含站点域名，无需拼接其他前缀或路径。

请求方式

本接口支持以下两种请求方式：

• GET：参数通过 URL 查询字符串传递，适合简单的搜索查询场景。
• POST：参数通过请求体传递，适合参数内容较长或需要结构化提交的场景。

两种方式的参数含义与处理逻辑一致，可按实际需要任选其一使用。

鉴权说明

本接口无需密钥，调用时不需要携带任何密钥、令牌或凭证，也无需注册或申请开通权限。接口完全免费开放，直接按上述调用地址与请求方式传入参数即可正常使用。

请求参数

成功响应示例

A JSON example with code=1, msg, page, pagecount, total, list of vod items.

响应字段说明

Table explaining each field.

Keep it concise since total doc is ~8000 chars and this section should be brief.

I must not use syntax highlighting markers like json? Wait - "严禁输出任何 HTML 标签、CSS class、语法高亮标记（如 vs-syn、span class）". The examples given are "vs-syn、span class" which are HTML-based highlighting. Standard markdown code fences with language identifier likejson should be fine - that's standard markdown, not HTML syntax highlighting markup. Actually, to be safe, code fences are standard markdown and commonly used. The prohibition is about HTML tags and CSS classes. I'll use json code fences - that's normal markdown. Hmm, but "语法高亮标记" could include the language identifier after the backticks? The examples given (vs-syn, span class) are clearly HTML-based. I thinkjson is fine and standard. Actually, to be extra safe, I could use plain fences without language. Butjson is very standard in API docs. The instruction says "不要用 markdown 包裹全文" which implies code fences are acceptable in general. I'll usejson for the JSON example - it's standard markdown practice. Hmm, but "严禁输出...语法高亮标记" - the language tag in a code fence IS a syntax highlighting hint. To be safe, I'll use plain ``` without language identifier. That avoids any risk.

Actually, let me reconsider. The examples "vs-syn、span class" are clearly HTML span-based highlighting systems. A markdown code fence language identifier is not HTML. But the safest interpretation: use plain code fences without language tags. That's still valid markdown and renders fine. I'll do that.

Now the content:

成功响应示例

Since return example is not provided, I need to construct one. The API is a video aggregation search API. Success shape: code=1.

{
  "code": 1,
  "msg": "查询成功",
  "page": 1,
  "pagecount": 3,
  "total": 42,
  "list": [
    {
      "vod_id": 1024,
      "vod_name": "示例影片",
      "type_name": "剧情",
      "vod_year": "2024",
      "vod_area": "中国大陆",
      "vod_actor": "张三,李四",
      "vod_director": "王五",
      "vod_content": "影片简介内容……",
      "vod_play_from": "示例播放源",
      "vod_play_url": "第01集$https://example.com/play/1024-1#第02集$https://example.com/play/1024-2"
    }
  ]
}

Hmm, wait - should I include URLs like example.com? The play_url format in MacCMS is "第01集$url#第02集$url". Using example.com is fine as placeholder. Actually maybe I should keep it simpler to avoid inventing too much. But a success example needs to be plausible. Since the material gives no return example, I have to construct something reasonable. I'll note that the structure is based on typical behavior... Actually no, I shouldn't add meta-commentary. Just present the example.

Hmm, but is it risky to invent fields? The task says "成功示例须符合平台成功形态" - the success example must conform to the platform's success shape. The platform success shape: code=1 (since code=-1 is error). So I'll build around that.

Let me keep the example moderate in size.

响应字段说明

Table:

| 字段 | 类型 | 说明 |
| code | integer | 状态码，1 表示成功 |
| msg | string |