# Origin/Destination sites

Segments and Deliveries always have an origin and a destination. Origin and destinations are called sites, that represent a stop a trucker is supposed to do in its journey.

The structuring fields for sites are:

Use the site object to specify instructions about the loading or unloading, planned arrival date and time at this point, or a reference specific to this place.

* `uid`: Dashdoc internal id for the site, unique in the whole Dashdoc database. It can be sent at creation to handle some specific use cases
* `address` : a Dashdoc address

A site can have an address, see [Company - Address](/docs/get-started/understand-the-data-model/company-address.md#addresses)

The `uid` makes a site unique. When a same site is used multiple times in a transport, it has the same `uid` and is the same entity. Take this example:

![Complex transport](/files/pkLzydjMM198dtLfMNeF)

Here, the site D is the destination of the segment 3, the delivery 1 and the delivery 2. When creating this transport using the API, the data sent for the site D must be the exact same.


---

# Agent Instructions: 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:

```
GET https://developer.dashdoc.com/docs/get-started/understand-the-data-model/site.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.