The Quotes object is used in the Get Quotes endpoint. There are many use cases for the Quotes in Bringg, including:

• Determining which teams and carriers are available and most effective for an order.
• Rate shopping by comparing carrier rates based on parameters like shipment dimensions, weight, destination, and desired delivery times.
• Embedding real-time quotes in your e-commerce platform to offer delivery options to your customers.
  Note: You can embed up to 4 carrier-provided slots or 30 own-fleet availability slots.

See the Get Quotes endpoint for sample response and request payloads and more information about using quotes to achieve different business goals.

Best Practices

• Since asap can mean different things to different carriers (different time spans, for example), including this parameter isn't always enough to signal an order's urgency or required delivery time to carriers. For this reason, we recommend including a pickup_window as well. This pickup_window can be set for one minute after the order creation time.
• Depending on your use case, it may be best to avoid including different pickup_window and dropoff_window durations in carrier quotes, as this can add unnecessary constraints for carriers. Instead, set the same, longer duration for each, allowing the carrier to complete the pickup and dropoff within that longer time frame at a pace that works best for them.

---

Request Data

Below is a list of all parameters that you can send to Bringg for this object. If there are attributes that you want to include but are not listed here, you can create custom attributes that can be displayed and used throughout Bringg.

For more details about how different parameter types such as datetime are formatted and used in Bringg, read our Data Formatting article.

📘

Best practice

We recommend using external IDs, which you define, in your requests. This reduces the need for you to map entities that already exist in your other systems.

For example, after creating a service plan in the Bringg UI or with the Create Service Plan endpoint, use the service_plan_external_id parameter when creating orders instead of mapping and sending tag_id and task_configuration_id.

Response and Webhook Data

Below is a list of the data returned in webhooks and responses to your API requests. The inclusion of specific parameters may depend on your use case, your API request, and the webhook fields you have subscribed to.