> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/starter-kit/faqs/technical-integration-faqs.md).

# Technical Integration FAQs

Ordering flows, iframes, and API access.

{% hint style="info" %}
Details available under NDA. [Request one now](mailto:hi@reachplatform.com).
{% endhint %}

<details>

<summary><strong>How would we iframe Reach into our online order process and agents' ordering tool?</strong></summary>

No rip-and-replace for agents. A swivel-chair integration sits alongside the tools they already use. For your customers, a separately hosted mobile web flow keeps things lightweight and your main site untouched. However, if you want to create a unified journey, we support iframing into your existing websites for end-customers.

[Request an NDA to learn more →](mailto:hi@reachplatform.com)

</details>

<details>

<summary><strong>What API capabilities are available?</strong></summary>

Reach is cloud-native, modular, and API-first — built to integrate, not to silo. Full API specs and documentation are available [here](https://docs.reachplatform.com/technical/api/product-lifecycle-api-overview).

[Request an NDA to learn more →](mailto:hi@reachplatform.com)

</details>


---

# 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.reachplatform.com/starter-kit/faqs/technical-integration-faqs.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.