> For the complete documentation index, see [llms.txt](https://docs.b2ihealthcare.com/snow-owl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2ihealthcare.com/snow-owl/8.x/index/explore/import.md).

# Import RF2 distribution

Let's import an RF2 release in `SNAPSHOT` mode so that we can further explore the available SNOMED CT APIs! To do so, use the appropriate request from the [SNOMED CT Import API](https://github.com/b2ihealthcare/snow-owl/blob/8.x/docs/api/snomed/import.md) as follows (the second `SNOMEDCT` in the request path represents the code system identifier):

```bash
curl -v http://localhost:8080/snowowl/snomedct/SNOMEDCT/import?type=snapshot\&createVersions=false \
-F file=@SnomedCT_RF2Release_INT_20170731.zip
```

Curl will display the entire interaction between it and the server, including many request and response headers. We are interested in these two (response) rows in particular:

```
< HTTP/1.1 201 Created
< Location: http://localhost:8080/snowowl/snomedct/SNOMEDCT/import/107f6efa69886bfdd73db5586dcf0e15f738efed
```

The first one indicates that the file was uploaded successfully and a resource has been created to track import progress, while the second row indicates the location of this resource.

{% hint style="info" %}
Depending on the size and type of the RF2 package, hardware and Snow Owl configuration, RF2 imports might take hours to complete. Official SNAPSHOT distributions can be imported in less than 30 minutes by allocating 6 GB of heap size to Snow Owl and configuring it to use a solid state disk for the data directory.
{% endhint %}

The process itself is asynchronous and its status can be checked by periodically sending a GET request to the location indicated by the response header:

```bash
curl http://localhost:8080/snowowl/snomedct/SNOMEDCT/import/107f6efa69886bfdd73db5586dcf0e15f738efed?pretty
```

The expected response while the import is running:

```json
{
  "id" : "107f6efa69886bfdd73db5586dcf0e15f738efed",
  "status" : "RUNNING"
}
```

Upon completion, you should receive a different response which lists component identifiers visited during the import as well as any defects encountered in uploaded release files:

```json
{
  "id" : "107f6efa69886bfdd73db5586dcf0e15f738efed",
  "status" : "FINISHED",
  "response" : {
    "visitedComponents" : [ ... ],
    "defects" : [ ],
    "success" : true
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.b2ihealthcare.com/snow-owl/8.x/index/explore/import.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.