Finalize prepared rich-text image uploads
Turn prepared rich_text_image uploads into stored images and get back their
public image_urls, in request order. Call this after PUTting each file to
its upload_url from POST /api/v1/attachments (purpose rich_text_image).
All-or-nothing: if any entry is invalid the whole request fails (422) with a
per-entry error under error_details, and nothing is consumed. Entries that
were already processed are remembered, so retrying with the same upload_ids
does not create duplicates. Embed the returned image_urls into your
rich-text HTML. No PAT scope required.
Authorizations
Personal Access Token prefixed with fh_. Sent as Authorization: Bearer fh_xxx.
The scope required by each endpoint is listed in that endpoint's description.
Body
upload_ids from POST /api/v1/attachments (purpose rich_text_image), each after its file was PUT to the upload_url. Finalized atomically: any invalid entry rejects the whole request, and already-processed entries are remembered so an identical retry does not duplicate them.
1 - 20 elements1Response
Images stored
Finalize-step response: the stored rich-text images, in the same order as the request upload_ids. Embed each image_url into your rich-text HTML (e.g. <img src="...">).