Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#2,809 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
javascript, markdown
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
JavaScript
Stelle
82
Fork
240
Merge medio
4g 2h
PR unite (30g)
44

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apify/apify-docs

Tutte le issue di apify/apify-docs

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.