GEgetanana
Content Management

Import Website From Capture

Changed on

Build the guide from the property's latest completed website capture.

The same job and polling as import_website, but the worker reads the pages the Website already shows instead of crawling the site a second time. The capture is the one the Sites board shows: newest by completion time (latest_completed_snapshots).

post/api/v1/content/properties/{property_id}/import-website/from-capture

Request

Path parameters

property_idstring uuid required

Request body

content_type'general' | 'dining'

Response

Successful Response

idstring uuid required
property_idstring uuid required
status'queued' | 'crawling' | 'structuring' | 'completed' | 'failed' required

Lifecycle of an async website-import job (see WebsiteImportJob).

A real multi-page property import takes 5–7 min (crawl + LLM structuring), which outlives client/proxy timeouts, so the work runs on the arq worker and the operator polls this status. QUEUED → CRAWLING → STRUCTURING → COMPLETED, or → FAILED at any point with a human-readable error_message.

urlstring required
source_refstring required
content_typestring required
source_pages_crawledinteger nullable
sources_totalinteger nullable
sources_doneinteger
error_messagestring nullable
created_atstring date-time required
updated_atstring date-time required
started_atstring date-time nullable
completed_atstring date-time nullable

Changes