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

# Contact us

Signposting on how to contact us if you have feedback on any of the documentation for our APIs.

## How to get in touch

We welcome customer feedback on OS APIs documentation. You can contact us using the [Contact us page on our website](https://www.ordnancesurvey.co.uk/contact-us).

## Leave feedback on individual pages

You can now leave a comment or feedback about a particular page on this documentation site by clicking the 'Was this helpful?' page feedback button option that's available on the top right-hand-side of each page, then entering a detailed comment / your feedback in the text box. The Technical Writers regularly review feedback left on this site, fixing any errors identified, improving content on the pages and simplifying customer user journeys. Your feedback will be anonymous.

<figure><img src="https://4043944746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoEzqrBzRGoJw7nQyLj1W%2Fuploads%2Fgit-blob-7c7e569dd5f90628720d655168c5845acd20b686%2FAPIs%20GitBook%20page%20feedback%20screenshot.png?alt=media" alt="Screenshot showing where customers can leave feedback on a page on this documentation site. The &#x27;Was this helpful&#x27; buttons on the top right-hand-side of a page are shown as is the text box underneath these buttons where customers can leave their comment on a page."><figcaption><p>Screenshot showing where customers can leave feedback on a page on this documentation site.</p></figcaption></figure>

{% hint style="info" %}

#### Tips for leaving actionable feedback for the Technical Writers

* **Explain what you were looking for in the documentation** – Describe the task or goal you were aiming to achieve when the issue occurred. Let us know what's missing or incorrect.
* **Clarify what you expected to see in the documentation** – Share what outcome or information you anticipated.
* **Describe the impact on your workflow** – Tell us how the issue affected your ability to complete your work.
* **Suggest helpful details that could be included in the documentation to help you** – Include any information that could assist someone facing the same situation.
  {% endhint %}


---

# 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.os.uk/os-apis/extra-links/contact-us.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.
