# Bevz Pick a Delivery Service for Onboarding API **Canonical:** https://apis.io/apis/bevz/bevz-pick-a-delivery-service-for-onboarding-api-api/ **Provider:** Bevz — https://apis.io/providers/bevz/ **Base URL:** https://api.bevz.com/integrator-service **Documentation:** https://docs.bevz.com/ Bevz Pick a Delivery Service for Onboarding API is one of 9 APIs that [Bevz](https://apis.io/providers/bevz/) publishes on the [APIs.io](https://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 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 ### Overview Onboarding 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 Flow 1. **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 ### Overview The 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 Flow 1. **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. ## Machine-readable artifacts (15) - **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/openapi/bevz-pick-a-delivery-service-for-onboarding-api-api-openapi.yml - **Documentation** — https://docs.bevz.com/ - **APIReference** — https://docs.bevz.com/ - **GettingStarted** — https://docs.bevz.com/#tag/Getting-Started - **Authentication** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/authentication/bevz-authentication.yml - **Conventions** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/conventions/bevz-conventions.yml - **ErrorCatalog** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/errors/bevz-problem-types.yml - **DataModel** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/data-model/bevz-data-model.yml - **Webhooks** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/asyncapi/bevz-webhooks.yml - **Sandbox** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/sandbox/bevz-sandbox.yml - **ChangeLog** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/changelog/bevz-changelog.yml - **Lifecycle** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/lifecycle/bevz-lifecycle.yml - **RateLimits** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/rate-limits/bevz-rate-limits.yml - **Conformance** — https://raw.githubusercontent.com/api-evangelist/bevz/refs/heads/main/conformance/bevz-conformance.yml - **Support** — https://docs.bevz.com/#tag/faq ## Other Bevz APIs (8) - [Bevz Integrator Users API](https://apis.io/apis/bevz/bevz-integrator-users-api/) - [Bevz Integrators API](https://apis.io/apis/bevz/bevz-integrators-api/) - [Bevz Lotto Scratcher Games API](https://apis.io/apis/bevz/bevz-lotto-scratcher-games-api/) - [Bevz Order API](https://apis.io/apis/bevz/bevz-order-api/) - [Bevz Store Products API](https://apis.io/apis/bevz/bevz-store-products-api/) - [Bevz Stores API](https://apis.io/apis/bevz/bevz-stores-api/) - [Bevz Uber Eats Onboarding API Workflow API](https://apis.io/apis/bevz/bevz-uber-eats-onboarding-api-workflow-api/) - [Bevz Webhooks API](https://apis.io/apis/bevz/bevz-webhooks-api/) --- Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/bevz/bevz-pick-a-delivery-service-for-onboarding-api-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/bevz/.