Burq Delivery API

Name: Burq Delivery API API
Brand: Burq Delivery API
Availability: InStock

✓ Official Vendor SpecE CommerceShipping LogisticsapiKey27 EndpointsREST

For Agents

Quote and dispatch on-demand and same-day local deliveries through multiple carriers, manage stores and orders, and build multi-stop routes via a single Burq integration.

Quickstart

Get started with Burq Delivery API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"dispatch a Burq delivery"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Burq Delivery API API.

Generate multi-provider delivery quotes via POST /quote

Create, initiate, and cancel deliveries through the deliveries surface

Track an existing delivery by ID and list recent deliveries

Create and update stores that act as pickup origins

Place, update, and cancel orders tied to a store

GET STARTED

Start building with Burq Delivery API API

Explore with Jentic

View OpenAPI Document

The Burq Delivery API is a delivery-orchestration platform that aggregates multiple last-mile delivery providers behind a single integration. It supports generating delivery quotes, creating and cancelling deliveries, managing stores and orders, building multi-stop routes, and reporting delivery incidents. Burq is used by retailers, restaurants, and platforms that want on-demand or same-day local delivery without integrating each carrier directly. Authentication is a single x-api-key header tied to the Burq account.

Use Cases

Patterns agents use Burq Delivery API API for, with concrete tasks.

★ On-demand local delivery for orders

Quote and dispatch a local delivery for each order placed in the merchant's storefront. POST /quote returns rates from multiple carriers; the merchant picks one and POST /delivery_information then POST /initiate_delivery hands the job to the chosen provider. Suitable for restaurants and retailers that need same-day delivery without contracting with each carrier separately.

POST /quote with the pickup and dropoff addresses, present the quote options, then POST /delivery_information and POST /initiate_delivery to dispatch the chosen provider.

Order and store management

Maintain stores as pickup origins and the orders attached to each store. The /stores and /orders endpoints support create, update, retrieve, and cancel, and orders can be paired with /orders/{id}/quotes and /quotes/{id}/accept to compare and lock in a delivery rate. Useful for multi-location merchants who manage their dispatch operations from a central system.

Create a store via POST /stores, add an order via POST /orders, request rates with POST /orders/{id}/quotes, and accept the chosen quote with POST /quotes/{id}/accept.

Multi-stop route delivery

Group several orders into a single multi-stop route to reduce per-order delivery cost. POST /routes/quotes returns route-level rates and POST /routes creates the route once a rate is accepted. Good for batch dispatch windows where multiple deliveries from the same store are headed to nearby destinations.

POST /routes/quotes with the list of pickups and dropoffs, present rates to the merchant, then POST /routes to lock in the route.

AI agent delivery dispatch via Jentic

An AI assistant can quote, dispatch, and track local deliveries on behalf of a merchant — for example, watching the order queue and triggering a Burq delivery automatically when an order is ready. Jentic vaults the Burq x-api-key and issues scoped, short-lived access for each call, so the raw account key never enters the agent's context.

Search Jentic for 'dispatch a Burq delivery', load the /initiate_delivery schema, and execute it once the merchant confirms the chosen quote.

Key Endpoints

27 endpoints — the burq delivery api is a delivery-orchestration platform that aggregates multiple last-mile delivery providers behind a single integration.

METHOD

PATH

DESCRIPTION

POST

/quote

Create delivery quotes from multiple carriers

POST

/delivery_information

Create a delivery

POST

/initiate_delivery

Initiate the chosen delivery

POST

/delivery/{id}/cancel

Cancel a delivery

GET

/delivery/{id}

Get a delivery

POST

/orders/{id}/quotes

Create order-level delivery quotes

POST

/quotes/{id}/accept

Accept an order quote

POST

/routes

Create a multi-stop route

POST

/quote

Create delivery quotes from multiple carriers

POST

/delivery_information

Create a delivery

POST

/initiate_delivery

Initiate the chosen delivery

POST

/delivery/{id}/cancel

Cancel a delivery

GET

/delivery/{id}

Get a delivery

Why though Jentic?

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

Credential isolation

The Burq x-api-key is stored encrypted in the Jentic vault. Agents receive a scoped, short-lived token per operation — the raw account key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'dispatch a Burq delivery') and Jentic returns the matching /quote or /initiate_delivery operation with its full request schema, so the agent calls the correct endpoint without reading Burq docs.

Time to first call

Direct Burq integration: 1-3 days for quote-then-dispatch wiring and webhook handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shippo API

Shippo focuses on parcel shipping with major carriers rather than on-demand local couriers.

Pick Shippo for traditional parcel shipping; pick Burq for on-demand and same-day local delivery.

Complementary

Akamai API

Akamai for edge security and CDN in front of merchant storefronts that integrate Burq.

Use Akamai alongside Burq when securing a high-traffic storefront whose checkout dispatches Burq deliveries.

Complementary

Stripe API

Stripe handles the customer payment that pairs with the Burq delivery dispatch.

Use Stripe to charge the customer for the order and Burq to deliver it; the two run side by side in checkout flows.

FAQs

Specific to using Burq Delivery API API through Jentic.

What authentication does the Burq Delivery API use?

Burq uses an x-api-key header containing the API key issued from the Burq account dashboard. Through Jentic, the key is encrypted in the vault and a scoped, short-lived token is issued per operation, so the raw account key never enters the agent's context.

How do I get a delivery quote and dispatch the chosen carrier?

POST /quote with pickup and dropoff addresses to receive multi-carrier rates. After choosing one, POST /delivery_information to create the delivery and POST /initiate_delivery to dispatch the selected provider. Track progress with GET /delivery/{id}.

Can I cancel a Burq delivery after it has been initiated?

Yes, POST /delivery/{id}/cancel cancels the delivery. Cancellation policies and any fees depend on the underlying carrier and the current status of the delivery.

Does Burq support multi-stop routes?

Yes. POST /routes/quotes returns rates for a batch of pickups and dropoffs and POST /routes creates the route once accepted. POST /routes/{id}/cancel cancels an active route.

What are the rate limits for the Burq Delivery API?

The OpenAPI spec does not declare explicit limits. Burq publishes throttle and pricing guidance in their docs — handle 429 responses with retry-with-backoff for high-volume quote requests.

How do I dispatch a Burq delivery through Jentic?

Run `pip install jentic` and search for 'dispatch a Burq delivery'. Jentic returns the /initiate_delivery operation, you load its schema, and execute the call with the prepared delivery payload — credentials stay in the Jentic vault.