> Agent-readable docs index: /llms.txt. Fetch only the needed Markdown pages first; use /docs.zip only for broad search after checking /docs-manifest.json or /docs.zip.sha256.

# Image

This is the API for images.

It provides features for generating upload URLs and registering Client images.

<details>
<summary>Key Concepts</summary>
<dl>
<dt>presigned URL</dt>
<dd><strong>Definition:</strong> A temporary upload URL issued to allow image files to be uploaded.<br /><strong>Description:</strong> Instead of sending files directly to the KOS API, upload the image binary to the URL in the response via a <code>PUT</code> request. The issued URL is valid for 5 minutes.</dd>
<dt>Client Image</dt>
<dd><strong>Definition:</strong> Image file information linked to and managed for a Client.<br /><strong>Description:</strong> After uploading a file, register it as a Client image by providing the file name, Client ID, image source, capture date and time, and other details.</dd>
<dt>Image Source</dt>
<dd><strong>Definition:</strong> A value that identifies where the image was generated.<br /><strong>Description:</strong> Indicates the context in which the image was created, such as in-clinic capture, Client capture, consent form, or pen chart.</dd>
<dt>Capture Device Code</dt>
<dd><strong>Definition:</strong> A code representing the device used to capture the image.<br /><strong>Description:</strong> Used to identify the capture device of an image by linking it to the device code managed by the clinic.</dd>
<dt>Image Classification Code</dt>
<dd><strong>Definition:</strong> A code used to classify images based on operational criteria.<br /><strong>Description:</strong> Used to organize images according to the image classification system defined by the clinic, such as progress photos or consultation materials.</dd>
<dt>Image Folder Path</dt>
<dd><strong>Definition:</strong> The path indicating the folder location to which an image belongs.<br /><strong>Description:</strong> Subfolders are separated by a slash (<code>/</code>), allowing Client images to be managed in a folder structure.</dd>
</dl>
</details>


## Endpoints

- [Issue image upload URL](/en/docs/openapi/generate-uploading-image-url.md): `POST /image/open/v1/commands/generate-uploading-url`
- [Register Client images](/en/docs/openapi/register-visitor-images.md): `POST /image/open/v1/commands/register-visitor-images`
