Refresh content

Asks Instagram for the account’s newest posts and reels. inDM pulls posts on a schedule rather than on demand, so a post published in the last few minutes is often missing from List media while it already exists on Instagram. This fetches it.

The refresh runs in the background. You get 202 with a job_id to poll with Get a refresh. Its status is started, or backfill when the account’s first full sync is still running and you were handed that job instead. When the account synced within the last minute there is nothing new to ask for, and you get 200 with status: "already_current" instead.

Needs a full key.

POST /accounts/{account_id}/refresh

Refresh content

cURL

curl --request POST \
  --url https://api.indm.social/v1/accounts/{account_id}/refresh \
  --header 'Authorization: Bearer <token>'

200

Example

{ "status": "already_current" }

Authorizations

Authorization · string · header · required

An API key from Settings → API keys in the inDM app, sent as Authorization: Bearer indm_.... Keys belong to one workspace and carry a scope: read for GET routes and the validate dry run, full for everything. Keep keys on your server; never ship one to a browser or a mobile app.

Path Parameters

account_id · string<uuid> · required

The account id from List accounts.

Response

200

application/json

The account synced within the last minute. Nothing was queued; read the media now.

status · enum<string> · required

started: a refresh is running; poll it. backfill: the account's first full sync is still running, and job_id is that sync. already_current: the account synced within the last minute, so nothing was queued; read the media now.

Available options: started, backfill, already_current

job_id · string<uuid>

The refresh job to poll with Get a refresh. Left out when status is already_current.