> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/get-started/embedding.md).

# Choose an integration

Planned Taptap3D website embedding for approved inventory listings and ecommerce storefronts.

The planned embed displays an approved inventory listing inside a website the business already operates. The business maintains the record in Taptap3D; its website presents the published result.

The feature is not released. There is no production embed URL, SDK package, API key flow or hosted sandbox to use today. The [connection playbook](/get-started/connection-playbook.md) specifies the proposed syntax and provides examples for integration planning and a local mock.

## Two integration surfaces

| Surface             | Choose it when                                                        | Client responsibility                                                              |
| ------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Hosted iframe       | You want a hosted item presentation inside an existing page.          | Product mapping, host HTML, fallback, frame policy and lifecycle handling.         |
| Public listing data | Your storefront needs its own layout or server-rendered item content. | Safe rendering, refresh/withdrawal handling, accessibility and asset presentation. |

Start with the [local quickstart](/get-started/local-quickstart.md) to see the proposed frame flow. Then follow [Embed a listing](/integration-guides/iframe-guide.md) or [Render listing data](/integration-guides/data-guide.md). Both surfaces are planned; neither replaces storefront checkout or stock management.

The first target is one item. A whole catalogue needs navigation, grouping, ordering and collection-level metadata; it is a separate integration surface.

## The proposed publication flow

1. Edit the inventory record and photographs.
2. Review public fields and image rights.
3. Approve a publication revision.
4. Add its embed to the host website.
5. Update or withdraw the publication when the record changes.

The proposed contract serves the latest approved revision when `revision` is omitted, or a pinned approved revision when it is supplied. Saving a private edit must not publish it. Withdrawal overrides both modes. This policy needs implementation and review before release.

## Ecommerce scope

An embed can present an object and link to an existing storefront or enquiry route. It does not imply a cart, payment gateway, bidding system or order-management service.

Channel-specific adapters follow the listing contract and a real integration partner. See [Listing contract](/proposed-reference/listing-contract.md) and [Roadmap](/project/roadmap.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taptap3d.com/get-started/embedding.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 `build a script that syncs our docs to a CMS` 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.