Skip to main content
Use https://data.grdd.net for the Connect operations on this page. Send Authorization: Bearer <ACCESS_TOKEN> with a Core-issued access token. 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. Do not send a body or an Idempotency-Key header on these GET requests. Use the Platform API for trip exchange between reservation systems. See Core compatibility for operations that these Connect routes do not replace.

List reservations and quote summaries

To list quotes, use activity=quotes on the same route. To include both reservations and quotes, omit activity. 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.
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. Keep the Core booking read 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: 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 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.
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 contract. 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.