> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/dev-kr/api-sdk/api-integration/3d-product-integration.md).

# 3D 상품 연동하기

파트너사 개발자가 Archisketch Open API를 처음 연동할 때 따라야 할 전체 흐름을 설명합니다.

Archisketch Open API를 연동하기 위한 전체 흐름입니다. 아래 순서대로 진행하세요.

## 1. x-api-key 발급

Archisketch 대시보드에 로그인한 후 API 키를 발급받습니다. 발급받은 `x-api-key`는 이후 모든 API 요청 헤더에 포함해야 합니다.

{% hint style="warning" %}
`x-api-key`는 외부에 노출되지 않도록 안전하게 보관하세요.
{% endhint %}

## 2. 모델링 등록

3D 모델 파일을 업로드하여 모델링을 생성합니다. 생성된 모델링 ID는 다음 단계에서 사용합니다.

{% content-ref url="/pages/w1ABpbjXhkHSmVC1d1K7" %}
[모델링 등록하기](/guide/dev-kr/api-sdk/api-integration/3d-product-integration/modeling.md)
{% endcontent-ref %}

## 3. 컴포넌트 등록

모델링을 기반으로 컴포넌트를 생성합니다. 생성된 컴포넌트 ID는 다음 단계에서 사용합니다.

{% content-ref url="/pages/jiDBj6GtgNkCvQpsp4AK" %}
[컴포넌트 등록하기](/guide/dev-kr/api-sdk/api-integration/3d-product-integration/component.md)
{% endcontent-ref %}

## 4. 파라메트릭 컴포넌트 등록 (선택)

치수·색상 등 파라미터를 동적으로 조합할 수 있는 파라메트릭 컴포넌트가 필요한 경우 진행합니다.

{% content-ref url="/pages/vsmN6rcmJQO12pSkaCVj" %}
[파라메트릭 컴포넌트 등록하기](/guide/dev-kr/api-sdk/api-integration/3d-product-integration/parametric.md)
{% endcontent-ref %}

## 5. 상품 등록

컴포넌트를 기반으로 판매 상품을 생성합니다.

{% content-ref url="/pages/9m6mTnEicpizWPZYVHzo" %}
[상품 등록하기](/guide/dev-kr/api-sdk/api-integration/3d-product-integration/product.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archisketch.com/guide/dev-kr/api-sdk/api-integration/3d-product-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.