canonical: https://jentic.com/apis/bring.com/bring # Bring ShippingGuide API Jentic publishes the only available OpenAPI specification for ShippingGuide API, keeping it validated and agent-ready. Bring's ShippingGuide API returns the available shipping services for a given sender-recipient combination together with estimated delivery times, prices, environmental data, and human-readable service descriptions and logos for checkout display. It is designed to power Nordic e-commerce checkouts where Bring (Posten Norge / PostNord-adjacent) is the dominant carrier across Norway, Sweden, Denmark, and Finland. Available services are filtered by the customer numbers attached to the requesting account, so each merchant sees the contractual rates and products they are entitled to use. ## For AI agents Get available Bring shipping services, prices, delivery times, and CO2 estimates for any Nordic sender-recipient pair. Useful for e-commerce checkouts and logistics quoting agents. ## Scope Does not handle label printing, pickup booking, or shipment tracking - use for shipping rate, ETA, and CO2 quoting only. ## Capabilities - Calculate shipping prices for parcels and pallets between any pair of postal codes Bring serves - Return estimated delivery dates so a checkout can show 'arrives Tuesday' messaging to the buyer - Surface CO2 emission estimates per service so merchants can offer greener shipping options - Filter the response by the customer numbers on the account, so only contracted services appear - Return service logos and localised descriptions ready to render in a checkout selector ## Use cases ### Nordic E-Commerce Checkout Rate Display Norwegian and Swedish online stores call ShippingGuide at checkout to render a list of available Bring services with price, ETA, and a recognisable carrier logo for each option. Because the API filters by the merchant's customer numbers, the buyer only sees services the merchant is actually contracted for and at the negotiated rate. A typical integration is a single POST per checkout session and adds under 200 ms of latency. Example prompt: POST `/api/v2/products` with sender postal code 0150 (Oslo) and recipient postal code 11122 (Stockholm) for a 3 kg parcel and return the cheapest service with its delivery date ### Sustainability-Driven Shipping Selection Brands with carbon-conscious customers use the CO2 estimates returned by ShippingGuide to surface a 'greenest option' badge in checkout. The agent compares emissions across services for the same lane and either auto-selects the lowest-impact option or shows the trade-off between price, speed, and emissions explicitly to the buyer. Example prompt: POST `/api/v2/products` for a 5 kg shipment from Oslo to Bergen and return the service with the lowest CO2 emission value ### Logistics Quoting for B2B Orders B2B sellers shipping pallets across the Nordics use ShippingGuide to generate accurate price quotes for sales reps before an order is confirmed. The same endpoint that powers consumer checkout returns enterprise services such as Bring Cargo, so a single integration covers both retail and business shipping flows. Example prompt: POST `/api/v2/products` with a pallet shipment of 200 kg from Trondheim to Copenhagen and return all cargo services with prices ### AI Shipping Agent Through Jentic An AI commerce agent uses Jentic to quote Bring shipping without holding the merchant's API key. The agent searches for 'quote a shipping rate', loads the ShippingGuide schema, and executes the call with the buyer's address. Combined with checkout and payment APIs through Jentic, the agent can complete an order end-to-end from natural-language input. Example prompt: Use Jentic to search 'quote a Bring shipping rate', load the bring.com operation, and execute it for a 2 kg parcel from Oslo (0150) to Stockholm (11122) ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v2/products` | Get available Bring shipping services with prices, delivery times, and CO2 estimates | ## Key resources - **Products** — Returns available shipping services with price, ETA, CO2, logo, and description for a sender-recipient pair ## Why Jentic - **Setup:** Wiring the Bring ShippingGuide by hand means supplying your API key and customer numbers, building the products request body, and parsing rate, ETA, and CO2 fields out of the response yourself. Through Jentic you install once, import the ShippingGuide API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** ShippingGuide exposes a single quoting operation that takes its shipment details in the request body, not as a resource id in the URL path, so scoping is operations-only: the agent is limited to the products quote operation and nothing else. You choose whether that one operation is allowed. - **Credential handling:** Your Bring API key and customer numbers are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'quote a shipping rate and delivery time', and Jentic returns the POST `/api/v2/products` operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ShipEngine** — Multi-carrier shipping rates and label generation across global carriers - **FedEx** — Global express shipping with rates, tracking, and labels - **DHL Shipment Tracking** — Track DHL shipments by tracking number with milestone events ## FAQ ### Why is there no official OpenAPI spec for ShippingGuide API? Bring does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ShippingGuide API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the ShippingGuide API use? Bring's ShippingGuide requires an API key tied to the user account, plus the customer numbers contracted with Bring passed in the request body. Through Jentic, the API key is stored encrypted in your Jentic One instance and the agent never handles the raw key. ### Can I get CO2 emission estimates per shipping service? Yes. The POST `/api/v2/products` response includes environmental data for each service so a checkout can display a CO2 figure alongside the price and ETA. This lets buyers choose between speed, cost, and sustainability. ### Which countries does Bring ShippingGuide cover? Coverage centres on the Nordic markets - Norway, Sweden, Denmark, and Finland - with cross-border services to the rest of Europe. The available services in any response are filtered by your merchant agreement and the sender-recipient postal codes you submit. ### How do I quote a shipping rate through Jentic? Search Jentic for 'quote a Bring shipping rate', load the bring.com ShippingGuide schema, and call POST `/api/v2/products` with sender, recipient, weight, and your customer number. Jentic supplies the API key automatically. ### Are there rate limits on the ShippingGuide API? Bring does not publish hard rate limits in the OpenAPI spec but applies fair-use throttling per account. For high-volume checkout traffic, cache responses by sender-recipient-weight tuple to reduce repeat calls and stay well under any throttling threshold. ### Can I limit what my agent is allowed to do with the ShippingGuide API? Yes. Because you run Jentic One yourself, your own rules decide which ShippingGuide operations and credentials the agent may use. The ShippingGuide API exposes a single quoting operation, POST `/api/v2/products`, which takes its shipment details in the request body rather than as an id in the URL, so scoping is operations-only: you choose whether the agent is allowed to call that one products quote operation at all. Your Bring API key and customer numbers stay with your instance and are injected only when you have permitted that call.