Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#2,809 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
javascript, markdown
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
82
Forks
240
Merge medio
4 d 2 h
PR fusionados (30 d)
44

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apify/apify-docs

Todos los issues de apify/apify-docs

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.