Bring ShippingGuide API

Name: ShippingGuide API
Brand: ShippingGuide API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceShipping LogisticsapiKey1 EndpointsREST

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

Install Jentic One Beta

Connect the ShippingGuide API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ShippingGuide API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ShippingGuide API.

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

GET STARTED

Start building with ShippingGuide API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use ShippingGuide API for, with concrete tasks.

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

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.

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.

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.

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

1 endpoints — jentic publishes the only available openapi specification for shippingguide api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v2/products

Get available Bring shipping services with prices, delivery times, and CO2 estimates

POST

/api/v2/products

Get available Bring shipping services with prices, delivery times, and CO2 estimates

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Bring API key and customer numbers are stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw key never enters prompts or logs.

Intent-based discovery

Agents search by intent such as 'quote a shipping rate' and Jentic returns the matching ShippingGuide operation with its parameter schema, so the agent can call it without browsing Bring's developer portal.

Time to first call

Direct ShippingGuide integration: 1-2 days including request modelling, response parsing, and contract negotiation with Bring. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using ShippingGuide API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.