Choose your task
Start with the Connect reservation and quotation reference onhttps://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.
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 defines the existing access modes.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 and the booking response fields.
Dashboard workflows and external calls
For manual work, use the Connect portal’s sending guide. 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 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:
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 andretryable 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, object model and receiving guide.