LLllmpulse
GEO Writer

Revert GEO Writer task content

Changed on

Discards every manual edit on the task and restores the output as it was generated. On a product_listing task, description_html comes back with only p, ul, ol, li, strong, em, h3 and br and no attributes, cleaned like an edit. Returns ERR_INVALID_PARAM when the task has no manual edits. Requires a read_write scope API key and, for team members, update permission on GEO Writer.

post/intelligence_tasks/{id}/revert

Request

  • Base URL
    https://api.llmpulse.ai/api/v1
  • URL
    https://api.llmpulse.ai/api/v1/intelligence_tasks/{id}/revert
  • Auth
    API key in header Authorization

Path parameters

idstring required

Numeric task ID or public_id string token

Query parameters

project_idinteger required

Project ID

Response

Task restored to its generated output

idinteger
public_idstring
project_idinteger
task_typestring
titlestring
statusstring
prompt_idinteger nullable
prompt_textstring nullable
agentic_modeboolean
custom_topicstring nullable
user_instructionsstring nullable
output_language_codestring nullable
word_countinteger nullable
result_dataobject nullable

The generated content once status is completed; null before that. A product_listing task returns title, summary, description_html (p, ul, ol, li, strong, em, h3 and br only), faq (question and answer pairs), seo_title, seo_description, image_alts (image_id and alt), changes (field and reason) and labels

error_messagestring nullable
estimated_timestring nullable
created_atstring date-time
processed_atstring date-time nullable
manually_edited_atstring date-time nullable

When the content was last edited by hand; null while the output is as generated

edited_by_user_idinteger nullable

User behind the last manual edit; null for an unedited task or an edit made from an embedded portal

result_versionstring

Concurrency token for content edits: send it back as result_version on PATCH /intelligence_tasks/{id} so an edit composed before a regeneration is refused with ERR_STALE_CONTENT (409). It is "0" until the task first completes, then changes each time a generation or regeneration replaces result_data, never on a manual edit or a revert. Treat it as opaque text

request_idstring

Example response

{
  "result_version": "1775642580"
}

Changes