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

# Ways to integrate

* [**Booking Widget**](https://sandbox.api.dronline.uk/api/partner/widget-docs) — a no-code embed. Add a snippet; we render the whole booking flow and take payment. Fastest to launch, least control over the look and flow.
* [**Connected API**](https://docs.dronline.uk/connected-api) — server-to-server REST. You build your own booking UI and run payment on your PSP; we run the clinical catalogue, scheduling, and patient records. More work, fully customisable.
* [**Platform API**](https://sandbox.api.dronline.uk/api/partner/platform-docs) *(in development)* — a full platform API where you manage your own practitioners, availability, appointment types, and patients on Dr.Online — the counterpart to Connected, where Dr.Online manages the catalogue. Not available yet; published so you can see the shape ahead of time.

The widget and Connected API share the same Dr.Online catalogue; choose whichever fits each surface.


---

# 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.dronline.uk/ways-to-integrate.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.