> ## 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.

# Connect reservations and quotations

> List reservations and quotes, read a transaction, and submit a standard quotation on the Connect API.

Use `https://data.grdd.net` for the Connect operations on this page. Send `Authorization: Bearer <ACCESS_TOKEN>` with a [Core-issued access token](https://docs.grdd.dev/connect-api/get-token.md). The list uses the company in your token. For an operator detail read, your company must be the requester or provider. A company role does not grant cross-company administrator access.

| Task | Method and path |
| - | - |
| List reservations or quote summaries | `GET /api/reservations` |
| Read a reservation by transaction ID | `GET /api/reservations/{transactionId}` |
| Read a quotation by transaction ID | `GET /api/quotations/{transactionId}` |
| Submit a standard quotation or trip payload | `POST /api/quotations` |

Do not send a body or an `Idempotency-Key` header on these `GET` requests. Use the [Platform API](https://docs.grdd.dev/platform-api/overview.md) for trip exchange between reservation systems. See [Core compatibility](https://docs.grdd.dev/connect-api/reservations/overview.md#compatibility-with-core) for operations that these Connect routes do not replace.

## List reservations and quote summaries

```bash theme={null}
curl --fail-with-body \
  'https://data.grdd.net/api/reservations?activity=reservations&limit=10' \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```

To list quotes, use `activity=quotes` on the same route. To include both reservations and quotes, omit `activity`.

| Query parameter | Values and behavior |
| - | - |
| `limit` | Page size, from 1 to 200,000. Default: 50. |
| `cursor` | The `nextCursor` value from the previous page. Keep the same filters and page size. |
| `locale` | `en`, `fr`, `de` or `es`. |
| `activity` | `reservations` or `quotes`. |
| `lastStatus` | `ACKNOWLEDGED`, `ASSIGNED`, `BOOKING_REQUEST`, `CANCEL`, `CLOSE`, `COMPLETE`, `CONFIRMED`, `EN_ROUTE`, `FAILED`, `NO_SHOW`, `ON_LOCATION`, `PASSENGER_ON_BOARD`, `Pending`, `QUOTE`, `REJECT` or `STOP`. |
| `sourceResNo`, `targetResNo` | Filter by source or target reservation number. Read the matching transaction by its returned `transactionId`. |
| `pickupDateStart`, `pickupDateEnd` | RFC 3339 timestamps. The start must not follow the end. |
| `deepSearch` | `true` or `false`. Use `true` to search beyond the standard list. |
| `fresh` | `true` or `false`. Use `true` to refresh the first page. It has no effect on a request with a cursor. |

A `200` response contains `items`, `nextCursor` and `total`. Each item has `transactionId`, requester `fromConextId`, provider `toConextId`, `isFarmout` and `canRetry`. Reservation numbers, status, dates and rating can be absent or `null`. Dates are UTC strings. Stop paging when `nextCursor` is `null`. The `total` counts matching list entries, not operational queues.

This response is a fixed summary. The list does not accept a company selector, offset, custom fields or the Core `format` parameter.

## Read a reservation or quotation

Replace `TRANSACTION_ID` with the ID returned by a list or submission. URL-encode the value if needed.

```bash theme={null}
curl --fail-with-body \
  "https://data.grdd.net/api/reservations/$TRANSACTION_ID?locale=en" \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```

| Operation | Optional query | `200` response |
| - | - | - |
| `GET /api/reservations/{transactionId}` | `locale` and `force=true\|false`. Use `force=true` for a fresh read. | `projection`, `reservation` and `capabilities`. The projection is `operational` or `legacy`. |
| `GET /api/quotations/{transactionId}` | `locale` only. Neither `force` nor the Core `cache` parameter applies. | `projection`, `quotation` and `capabilities`. An active quote has a `full` or `operational` projection. A record outside the active quote state has an `operational` or `legacy` booking projection in `quotation`. |

Use `locale=en`, `fr`, `de` or `es` for either operation. Read `projection` before choosing which fields to use:

* `operational` gives the transaction, status and party information. An operational quote also has fields such as `preferredVehicleType` and `passengerCount`.
* `legacy` is a booking view for eligible callers. It can include `locations`, `reservationDispatch` and `fees`. It does not return the original Core `tripPacket`.
* `full` is the richer active quote view. It can include `locations`, `passengers`, `fees` and totals.

For ordinary operator callers, the richer views require an `OWNER`, `MANAGER` or `ADMIN` role in a company that can read the record. Fields can still be absent, `null` or limited by the record and disclosure rules. A capability flag does not define a Connect mutation endpoint.

If you cannot read the requested record or it does not exist, the API can return `404 not_found`. If authentication fails, it returns `401 unauthenticated`. Invalid parameters return `400 invalid_request`. A dependency failure can return `502 downstream_failure`, `503 temporarily_unavailable` or `504 deadline_exceeded`. See [Connect API errors](https://docs.grdd.dev/connect-api/content/api-conventions.md#errors).

Keep the [Core booking read](https://docs.grdd.dev/connect-api/bookings/get-booking.md) if your integration needs `success` and `data`, the original `tripPacket` or an existing Core access mode.

## Submit a standard quotation

Send `POST https://data.grdd.net/api/quotations` with the access token of a user who can submit quotations for your company and `Content-Type: application/json`. The submitting user must still have a valid Core session. Use the complete standard quotation or trip JSON that your existing submission workflow accepts. Connect does not define a smaller trip payload. Do not send `Idempotency-Key`. The request is rejected with `400 invalid_request` and `reason: "idempotency_key_not_accepted"` if you include it.

The JSON body carries the complete standard submission, without an outer `data` wrapper. These ordinary fields have the following accepted types when present:

| Field | Accepted type |
| - | - |
| `transactionId` | String, 1 to 128 characters. |
| `resNo` | String or number. |
| `reservationType` | String. |
| `affiliateReservation` | Object with optional string fields `requesterId`, `providerId` and `status`, plus the other fields required by your standard payload. |

Other standard payload fields are forwarded and remain subject to submission validation. This field table is not a complete trip model. Do not send a minimal object from this table as a valid trip. If you do not have an accepted standard payload, obtain your integration's field mapping from [GRiDD support](mailto:support@grdd.net) before sending. The Platform request model is not declared interchangeable.

This example reads your complete payload from a local file. Running it submits a transaction. Use it only for a submission you intend to make.

```bash theme={null}
curl --fail-with-body --request POST \
  'https://data.grdd.net/api/quotations' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data-binary @complete-quotation.json
```

A `201` confirms the submission and contains its `transactionId`. This method does not update, convert or resend an existing quotation. It is not the [Platform send trip](https://docs.grdd.dev/platform-api/reservations/send-trip.md) contract.

| HTTP status and code | Meaning |
| - | - |
| `401 unauthenticated` | The API could not authenticate the submitting user or establish eligibility to submit. |
| `422 domain_rejected`, reason `core_rejected` | The submission was rejected. |
| `503 temporarily_unavailable`, reason `core_unreachable` | The submission service was unavailable. |
| `504 deadline_exceeded`, reason `core_outcome_unknown` | The API could not confirm whether the submission succeeded. |

**Do not automatically resend after an unknown outcome.** The receiving partner may already have the trip. Check your existing records or contact the receiving partner before deciding whether to submit again. Do not use `retryable: true` alone to make that decision.


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