> 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/gnet.md).

# GNet

Receive and send trips through the GNet network.

The GNet integration lets you receive trips from GNet partners (**Farm In**) and send trips to them (**Farm Out**). Open **Integrations → GNet**. The page has two tabs: **Connection settings** and **Vehicle type mapping**.

## Connection settings

| Setting                                                  | What it does                                                                                     |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Enable GNet integration**                              | Turns the integration on.                                                                        |
| **Receive bookings (Farm In)**                           | Accept new, updated and cancelled trips from GNet.                                               |
| **Send bookings (Farm Out)**                             | Allow sending trips to GNet.                                                                     |
| **API Gateway user (uid)** / **API Gateway secret (pw)** | Your GNet platform API credentials.                                                              |
| **Our GNet ID (requesterId)**                            | Your company's GNet ID, used when you send trips.                                                |
| **Partner GNet ID (providerId)**                         | The default partner for trips you send.                                                          |
| **Platform API base URL**                                | The GNet API address.                                                                            |
| **Farm In Basic Auth user** / **password**               | The credentials GNet uses when it sends trips to you.                                            |
| **Send the driver's name and phone number**              | Include the driver's contact details in status updates.                                          |
| **Send the driver's last known position**                | Forward live GPS to GNet while a trip is in progress.                                            |
| **Send notification to clients**                         | Email or SMS the passenger of a farm-in trip. When off, only the admin and company are notified. |

Click **Save**, then **Test token** to check the connection.

## Vehicle type mapping

Map each GNet vehicle type (for example *Sedan (standard)*, *SUV*, *Van (8 passenger)*, *Mini Bus*) to one of your [vehicle classes](/documentation/fleet-and-pricing/vehicle-classes.md). The mapping is used for both received and sent trips.

{% hint style="info" %}
You need a GNet account and credentials from GNet before you can connect.
{% endhint %}

Read more about the [GNet integration](https://codico.io/taxi-dispatch-software/gnet-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/gnet.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.