Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

No API or MCP support for publishing an Actor task (publicConfig silently ignored)

オープン
  • 何か問題がありますか？
#2,809 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
静か
技術スタック
javascript, markdown
領域
documentation

調査の方向性

Start with the existing “Publish your Actor task” documentation page linked in the issue and compare its Console instructions with the API and MCP capabilities described here. The request spans documenting the current limitations and potentially documenting or changing API behavior; confirm the intended scope with maintainers. Done means the publishing surface and unsupported behavior are accurately explained, or the agreed API change is documented.

索引モデルが issue の本文から書いたものです。

説明

Summary

Publishing an Actor task is currently Console-only. There is no public API endpoint and no MCP tool for it, even though the Actor quality score actively recommends "Publish a task for your Actor" and the docs allow up to 50 tasks per Actor.

For a publisher with dozens of Actors this makes the recommended action a manual, per-task click-through in Console.

What I tried (API)

  1. POST /v2/actor-tasks and PUT /v2/actor-tasks/{taskId} accept only name, title, options, input, actorStandby (per Update task).
  2. The response of both endpoints contains a publicConfig field (null for an unpublished task), but sending publicConfig in a PUT body is silently ignored — no error, and the field stays null:
// PUT /v2/actor-tasks/{id}  {"publicConfig": {"slug":"...","seoTitle":"...","seoDescription":"..."}}
// -> 200 OK, but response still has:  "publicConfig": null
  1. Guessed sub-resources all return page-not-found:
    • GET|PUT|POST /v2/actor-tasks/{id}/publication → 404
    • POST /v2/actor-tasks/{id}/publish → 404

What I tried (MCP)

mcp.apify.com (apify-mcp-server v0.12.0) exposes 11 tools — search-actors, fetch-actor-details, call-actor, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, search-apify-docs, fetch-apify-docs, report-problem, apify--rag-web-browser. None of them can create or publish a task, so the MCP route is not an alternative either.

Requests

  1. Document the publishing surface. Publish your Actor task describes only the Console flow; it would help to state explicitly that no API support exists today (so people stop reverse-engineering publicConfig).
  2. Expose it in the API — either document publicConfig as writable on PUT /v2/actor-tasks/{taskId}, or add a dedicated endpoint, with the same fields the Console form has: slug, SEO title, SEO description, displayed input fields, dataset view.
  3. At minimum, fail loudly. Right now an unsupported publicConfig in the request body is accepted with 200 OK and silently dropped, which looks like a successful write.

Why it matters

Published tasks are indexed by search engines and exposed as .md to AI agents, and Console's Insights recommends them as a quality-score item. Bulk publishing is exactly the kind of repetitive work an API should cover — currently the only path is N × manual Console forms.

Related: #2782, #2783.

主要言語
JavaScript
スター
82
フォーク
240
平均マージ
4日 2時間
マージ済み PR（30日）
44

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apify/apify-docs のほかの issue

apify/apify-docs の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。