The Bevz Integrator Service is a partner REST API that lets POS vendors and third-party integrators provision and manage stores on the Bevz platform programmatically. It covers store creation, provisioning and deprovisioning; menu upload in CSV or JSON with configurable column mapping and asynchronous status tracking; menu synchronization out to the connected delivery services; product catalog maintenance with per-service pricing and availability; the full order lifecycle from receipt through acceptance, out-for-delivery, completion, rejection and cancellation; post-acceptance order adjustments; and delivery-service onboarding for DoorDash and Grubhub via a single call plus a dedicated three-step OAuth handshake for Uber Eats. Three outbound webhooks push order events, menu upload status and store settings changes. Authentication is a bearer JWT with a 30-day lifetime, minted from Bevz-issued integrator credentials.
This API exposes
30 operations
across 24 paths,
organized into 8 resource areas,
and defines 12 schemas.
It is described by OpenAPI 3.0.3, at version 1.12.0.
Requests are made against 2 base URLs: https://api.bevz.com/integrator-service, https://sandbox-api.bevz.com/integrator-service.
30 operations24 paths12 schemas1 DELETE10 GET5 PATCH13 POST1 PUT
Metadata
The identity and technical contract details declared by the specification.
Across 24 paths, the API surfaces 30 operations — 1 DELETE, 10 GET, 5 PATCH, 13 POST, 1 PUT. They span 8 resource areas: Integrators, Stores, integrator_users, Store Products, Lotto Scratcher Games, Order, Pick a Delivery Service for Onboarding API, Uber Eats Onboarding API Workflow. Each is listed below with its method, path, parameters, and response codes.
Store Products refer to inventory items that are available in a specific store. These products can be managed, updated, and retrieved through the Store Products API.
Lotto Scratcher Games Retrieve lottery scratch-off game data from supported state lotteries. This endpoint provides game catalogs that can be used to display lotto ticket informat…
This document outlines the integration flow for onboarding new DoorDash and Grubhub stores through the [Delivery Services Onboarding API](tag/Pick-a-Delivery-Service-for-Onboardin…
The Uber Eats API allows you to onboard your store to Uber Eats and manage related operations. Uber Eats onboarding is a three-step process: 1. Generate OAuth URL: Obtain an autho…
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are StoreProducts (17 properties), Order (15 properties), LottoScratcherGame (12 properties), Store (11 properties). Each schema is shown below with its type and property counts.
JWT
object
4 properties
Menu
object
7 properties
User
object
Represents an integrator user account on the Bevz platform. This object contains all essential information about the user, including identity, authentication c…
8 properties
Store
object
Represents a retail store managed on the Bevz platform. This object contains all essential information about the store, including its identity, contact details…
11 properties
IntegratorMenu
object
Represents a menu upload payload for an integrator on the Bevz platform. This schema allows integrators to upload or synchronize their store menu, with support…
5 properties1 required
Order
object
Represents a customer order placed through the Bevz platform. This schema includes all relevant details about the order, such as products, delivery information…
15 properties
StoreProducts
object
Represents a product available for sale in a specific store on the Bevz platform. This schema includes product identity, categorization, inventory, pricing, an…
17 properties
LottoScratcherGame
object
12 properties
CreateStore
object
3 properties
DeliverySettings
object
1 property1 required
DeliverySettingsGH
DeliverySettingsDD
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Bevz Integrator Service, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
