Bevz Pick a Delivery Service for Onboarding API
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-Onboarding-API/operation/onboard).## DoorDash Onboarding### OverviewOnboarding a store to DoorDash is an asynchronous process initiated by Bevz via a webhook. Once the POS sends a request to the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard), DoorDash processes the information, performs necessary checks, and notifies Bevz of the outcome through a webhook.### Process Flow1. **Initiate Onboarding Request**- The POS sends a request to the Delivery Services Onboarding API with all required store and sensitive information.- Refer to the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard) for required fields.2. **DoorDash Processing**- DoorDash attempts to map the store using the provided details, requests approval from the merchant, and performs internal checks such as menu QA and business admin verification.3. **Receive Webhook Notification**- Once DoorDash completes processing, they send a webhook notification to Bevz indicating the onboarding status (e.g., approved, pending, rejected) and any relevant details or next steps.4. **Finalize Onboarding**- The integration is activated once all requirements and approvals are met. If issues arise (e.g., missing hours, menu errors, compliance problems), DoorDash notifies the merchant and Bevz for resolution.## Grubhub Onboarding### OverviewThe onboarding process enables POS systems to initiate a Grubhub store onboarding request via the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard). Bevz provides an auto-populated onboarding form, which the POS can present to the store. After submission, a Grubhub representative contacts the store to complete setup.### Process Flow1. **Initiate Onboarding Request**- The POS sends a request to the Delivery Services Onboarding API.- This request contains the required store information (e.g., store details, sensitive data).2. **Generate Onboarding Link**- Bevz responds with a unique onboarding link.- This link points to a form that is pre-filled with store data provided in step 1.3. **Customer Completes Form**- The POS system embeds or redirects the store to the generated onboarding link.- The store reviews and completes the form.4. **Grubhub Representative Follows Up**- Once the store submits the form, the information is sent to Grubhub.- A Grubhub representative contacts the store to finalize onboarding and assist with setup.
Bevz Pick a Delivery Service for Onboarding API is one of 9 APIs that Bevz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.
This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.2.0, 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.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
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…
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is DeliverySettings (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bevz 8
Other APIs Bevz publishes across the network.
This is an independent, third-party profile of Bevz Pick a Delivery Service for Onboarding API, 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.