> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/integrations/hq-travel.md).

# HQ Travel

Receive corporate bookings from HQ Travel's HQ Connect network.

CodiCo Dispatch can receive bookings from **HQ Travel / HQ Connect**, a vetted supplier network for corporate ground transport. The integration already exists, so you don't need to build anything yourself. **Integrations → HQ Travel** explains the process.

{% stepper %}
{% step %}

### Apply to HQ Connect

Apply to become a supplier at [hqtravel.com/hqconnect](https://hqtravel.com/hqconnect/). HQ Travel's Supply Management team reviews each supplier.
{% endstep %}

{% step %}

### Complete approval and contracting

Pass HQ Travel's supplier qualification, provide the documents they ask for and sign the commercial agreement.
{% endstep %}

{% step %}

### Set up billing

Agree invoicing, billing and payment directly with HQ Travel.
{% endstep %}

{% step %}

### Contact CodiCo

When HQ Travel has approved you, contact the CodiCo team. CodiCo provides HQ Travel with the technical details and configures your CodiCo Dispatch account.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
A CodiCo Dispatch account does not give you access to HQ Travel bookings. HQ Travel must approve your company first. CodiCo cannot approve you for HQ Connect.
{% endhint %}

Read more about the [HQ Travel integration](https://codico.io/taxi-dispatch-software/hq-travel-integration/) on the CodiCo website.


---

# 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://codico-dispatch.gitbook.io/documentation/integrations/hq-travel.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.