Bolt Bolt Food API
The Bolt Food API API from Bolt — 0 operation(s) for bolt food api.
The Bolt Food API API from Bolt — 0 operation(s) for bolt food api.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/bolt-eu-bolt-food-api-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Bolt Food API
version: '1.0'
description: 'Partner API for restaurants integrating point-of-sale (POS) systems with the Bolt Food delivery application - push and manage menus, accept, reject, and fulfill orders, manage dine-in orders created by waiters, and control store availability. Bolt also calls partner-hosted webhooks for new orders, cancellations, updates, provider status, courier details, and deductions. Access is partner-gated: an integrator ID and HMAC secret are issued by Bolt when a test account is created. This document is an API Evangelist summary of the official Redocly-published spec at developer.bolt.eu - the endpoint paths, methods, server, webhooks, and authentication are taken verbatim from the upstream spec, while request and response schemas are summarized rather than reproduced in full.'
contact:
url: https://developer.bolt.eu/
license:
name: Bolt Terms and Conditions
url: https://bolt.eu/en/legal/
x-endpoints-modeled: false
x-schemas-summarized: true
x-source: 'https://developer.bolt.eu/food/main/ (upstream spec: https://developer.bolt.eu/versions/98.0.0/docs/food/main.yaml)'
servers:
- url: https://node.bolt.eu/delivery-provider-pos
description: Production
security:
- boltHmacSignature: []
tags:
- name: Bolt Food API
paths: {}
webhooks:
sendNewOrder:
post:
operationId: webhook-sendNewOrder
summary: Bolt sends a new order to the partner-hosted endpoint for acceptance.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
sendCancelOrder:
post:
operationId: webhook-sendCancelOrder
summary: Bolt notifies the partner-hosted endpoint that an order was cancelled.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
sendOrderUpdate:
post:
operationId: webhook-sendOrderUpdate
summary: Bolt sends order state updates to the partner-hosted endpoint.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
sendProviderStatus:
post:
operationId: webhook-sendProviderStatus
summary: Bolt notifies the partner-hosted endpoint of provider (store) status changes.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
sendCourierDetails:
post:
operationId: webhook-sendCourierDetails
summary: Bolt sends courier details for an order to the partner-hosted endpoint.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
sendDeductionEvent:
post:
operationId: webhook-sendDeductionEvent
summary: Bolt sends deduction (financial adjustment) events to the partner-hosted endpoint.
description: Outbound webhook - Bolt POSTs to a partner-hosted endpoint. Documented upstream at https://developer.bolt.eu/food/main/.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SummarizedRequest'
responses:
'200':
description: Partner acknowledges the event.
tags:
- Bolt Food API
components:
schemas:
SummarizedRequest:
type: object
description: Request body summarized - see the official Bolt developer portal for the full documented schema of each operation.
additionalProperties: true
securitySchemes:
boltHmacSignature:
type: apiKey
in: header
name: x-external-integrator-id
description: Partner-gated HMAC request signing. Every request carries the integrator ID in `x-external-integrator-id` plus a `x-server-authorization-hmac-sha256` header containing the base64-encoded HMAC-SHA256 signature of the raw payload, computed with a secret key issued by Bolt. Webhook calls from Bolt to the partner authenticate with Basic auth or a partner-hosted identity server issuing bearer tokens.
externalDocs:
description: Bolt Food API reference on the Bolt developer portal
url: https://developer.bolt.eu/food/main/