Profiles

Backfill posts

Walks the profile's feed backwards from the newest post, importing in batches of 25, until it reaches from or the platform stops returning posts. Runs in the background - the response is the post sync record, which you poll for progress.

Billing: Request · Rate limit: 60/min

post/v1/social/profiles/{id}/backfill_posts

Request

  • Base URL: https://apihub.co.il
  • URL: https://apihub.co.il/v1/social/profiles/{id}/backfill_posts
  • Auth: HTTP bearer

Path parameters

idstring required

Profile id

Headers

Idempotency-Keystring

Replay-safe: the same execution is returned instead of charging twice

X-Tagstring

Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…

Request body

fromstring required

ISO 8601 date/time, or a bare date meaning that date's start of day. The run stops at the first post published before this.

Response

Completed

idstring

Execution id — stable across internal retries; use it with GET /v1/executions/{id}

status'pending' | 'processing' | 'completed' | 'partial' | 'failed' | 'cancelled' | 'timeout'
operationstring
tagstring nullable

Your X-Tag, if sent

created_atstring date-time
completed_atstring date-time nullable
outputobject

Operation result (see each operation). While a Studio render is processing: stage (queued · transcribing · downloading · preparing · cleaning_voice · mixing_audio · rendering · finishing), phase (the engine's: download · prepare · voice · audio · encode · qa · upload, or null), progress (a percent, 0–100) and progress_fraction (0–1), eta_seconds (seconds left, never below 0) and estimate_seconds

errorstring nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.