> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grdd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Reservations and quotations

> Use Connect to list and read transactions or submit a quotation. Find retained Core and Platform contracts.

## Choose your task

Start with the [Connect reservation and quotation reference](https://docs.grdd.dev/connect-api/reservations/connect-reservations.md) on `https://data.grdd.net`. Use the Platform API for trip exchange between reservation systems. Keep the Core booking read if you need its original response or access mode.

| Task | Reference |
| - | - |
| List reservations or quote summaries for your company | [List on Connect](https://docs.grdd.dev/connect-api/reservations/connect-reservations.md#list-reservations-and-quote-summaries). |
| Read a reservation or quotation by transaction ID | [Read on Connect](https://docs.grdd.dev/connect-api/reservations/connect-reservations.md#read-a-reservation-or-quotation). |
| Submit a standard quotation | [Submit on Connect](https://docs.grdd.dev/connect-api/reservations/connect-reservations.md#submit-a-standard-quotation). |
| Exchange a trip or supported quotation payload between reservation systems | [Platform send trip](https://docs.grdd.dev/platform-api/reservations/send-trip.md) and [sending reservations](https://docs.grdd.dev/platform-api/sending-reservations.md). |
| Read a booking through an existing Core integration | [Get booking by transaction ID](https://docs.grdd.dev/connect-api/bookings/get-booking.md). |
| Read a reservation through Platform | [By transaction ID](https://docs.grdd.dev/platform-api/reservations/get-by-transaction-id.md) or [by reservation ID](https://docs.grdd.dev/platform-api/reservations/get-by-reservation-id.md). |
| Cancel a trip | [By transaction ID](https://docs.grdd.dev/platform-api/reservations/cancel-by-transaction-id.md) or [by reservation number](https://docs.grdd.dev/platform-api/reservations/cancel-by-resno.md). |
| Retry a failed transaction | [Platform retry](https://docs.grdd.dev/platform-api/reservations/retry.md). This is not permission to resend a submission with an unknown outcome. |
| Send provider updates | [By transaction ID](https://docs.grdd.dev/platform-api/provider-updates/update-by-transaction-id.md) or [by reservation number](https://docs.grdd.dev/platform-api/provider-updates/update-by-resno.md). |
| Read trip tracking | [Platform tracking](https://docs.grdd.dev/platform-api/tracking/location-by-transaction-id.md) or the [GPS location service](https://docs.grdd.dev/connect-api/location/overview.md), according to your integration. |

## Read a booking on Core

Use your approved Core access token and the transaction ID of a booking you are allowed to read. The [booking reference](https://docs.grdd.dev/connect-api/bookings/get-booking.md#who-can-read-a-booking) defines the existing access modes.

```bash theme={null}
CORE_BASE_URL="<CORE_BASE_URL>"
ACCESS_TOKEN="<ACCESS_TOKEN>"
TRANSACTION_ID="<TRANSACTION_ID>"

curl --include --fail-with-body \
  "$CORE_BASE_URL/api/reservation/$TRANSACTION_ID" \
  --header "Authorization: Bearer $ACCESS_TOKEN"
```

Set `CORE_BASE_URL` to the Core host for your environment, not the Connect API host. A successful response has `success: true` and the booking in `data`. See [Core hosts](https://docs.grdd.dev/connect-api/core/overview.md#hosts) and the [booking response fields](https://docs.grdd.dev/connect-api/bookings/get-booking.md#response-fields).

## Dashboard workflows and external calls

For manual work, use the [Connect portal's sending guide](https://docs.grdd.dev/gnet-connect/sending-trips.md). Some portal workflows have no corresponding Connect API operation on this page. A capability in a reservation response does not define an endpoint or grant permission on another service. Ask [GRiDD support](mailto:support@grdd.net) if the documented operations do not cover your task.

## Compatibility with Core

Connect reservation reads do not replace these four groups of existing Core capabilities:

| Difference | What to keep |
| - | - |
| Changes to an existing reservation | Cancellation, amendment, status changes, rejection, retry and deletion still have Core-backed workflows. Use the published Platform cancellation, retry and provider-update methods where they cover your task. This reference does not add direct external Core mutation instructions for the remaining workflows. |
| Operational counts and gBook workflows | Operational counts, queue workflows and gBook still use Core-backed paths. The [gBook portal guide](https://docs.grdd.dev/gnet-connect/sending-trips.md) describes the user workflow, not a new public Connect API. |
| Driver and trip synchronization | Driver-information synchronization and trip updates still have Core-backed paths. Creating or linking a [vehicle content record](https://docs.grdd.dev/connect-api/content/vehicles.md) does not synchronize a reservation. Use the published Platform provider-update contract where applicable. |
| Distinct Core platform-admin cross-company read | The existing [Core booking read](https://docs.grdd.dev/connect-api/bookings/get-booking.md#who-can-read-a-booking) includes its GRiDD platform `ADMIN` access mode. Do not assume a Connect read has the same cross-company mode or response. Ordinary company-manager access is not platform-admin access. |

These differences do not make the entire reservation domain Core-only. They mean that a change of host or a similar route name is not a compatible replacement.

## Submission and retry safety

A timeout or server error can occur after GNet receives a trip. Do not automatically submit the trip again. Check the existing reservation or contact the receiving partner before resending. Follow the supported operation's outcome rules. Content API pending-operation and `retryable` rules are not a general trip-submission retry policy.

Platform retains its own base URL, token header, request models and callbacks. Continue to use its [authentication](https://docs.grdd.dev/platform-api/authentication/get-token.md), [object model](https://docs.grdd.dev/platform-api/reference/object-model.md) and [receiving guide](https://docs.grdd.dev/platform-api/receiving-reservations.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.