---
title: "Trigger C-STORE SCU"
method: POST
path: "/modalities/{id}/store"
tags: ["Networking"]
---

# Trigger C-STORE SCU

`POST /modalities/{id}/store`

Start a C-STORE SCU command as a job, in order to send DICOM resources stored locally to some remote DICOM modality whose identifier is provided in the URL: https://book.orthanc-server.com/users/rest.html#rest-store-scu

## Path parameters

- `id` string, required

## Request body

- object
  - `Asynchronous` boolean — If `true`, run the job in asynchronous mode, which means that the REST API call will immediately return, reporting the identifier of a job. Prefer this flavor wherever possible.
  - `CalledAet` string — Called AET that is used for this commands, defaults to `AET` configuration option. Allows you to overwrite the destination AET for a specific operation.
  - `Host` string — Host that is used for this commands, defaults to `Host` configuration option. Allows you to overwrite the destination host for a specific operation.
  - `LocalAet` string — Local AET that is used for this commands, defaults to `DicomAet` configuration option. Ignored if `DicomModalities` already sets `LocalAet` for this modality.
  - `MoveOriginatorAet` string — Move originator AET that is used for this commands, in order to fake a C-MOVE SCU
  - `MoveOriginatorID` number — Move originator ID that is used for this commands, in order to fake a C-MOVE SCU
  - `Permissive` boolean — If `true`, ignore errors during the individual steps of the job.
  - `Port` number — Port that is used for this commands, defaults to `Port` configuration option. Allows you to overwrite the destination port for a specific operation.
  - `Priority` number — In asynchronous mode, the priority of the job. The lower the value, the higher the priority.
  - `Resources` string[] — List of the Orthanc identifiers of all the DICOM resources to be sent
  - `StorageCommitment` boolean — Whether to chain C-STORE with DICOM storage commitment to validate the success of the transmission: https://book.orthanc-server.com/users/storage-commitment.html#chaining-c-store-with-storage-commitment
  - `Synchronous` boolean — If `true`, run the job in synchronous mode, which means that the HTTP answer will directly contain the result of the job. This is the default, easy behavior, but it is *not* desirable for long jobs, as it might lead to network timeouts.
  - `Timeout` number — Timeout for the C-STORE command, in seconds

## Response `200`

- object
  - `ID` string — In asynchronous mode, identifier of the job
  - `Path` string — In asynchronous mode, path to access the job in the REST API

---

[API](https://skmtc.net/orthancserver/apis/orthanc-server.md) · [All operations](https://skmtc.net/orthancserver/apis/orthanc-server/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/orthancserver/orthanc-server/versions/af646f6f871b/schema)