# Voosh API Documentation ## Overview Voosh aggregates data from multiple platforms, including DoorDash, Uber Eats, ezCater, Grubhub, and others, to provide a unified system that enables restaurant owners to analyze their listed restaurants across various platforms and locations. This API documentation outlines the available endpoints that facilitate seamless access to key operational data. These APIs empower restaurants to efficiently manage operations and make data-driven decisions. ### **API Environment & Access** Once you become an official Voosh partner, you will receive a unique **API key (partner token)** for secure authentication and access to live data. For partnership inquiries, please [contact us](https://voosh.ai/). ### Rate Limiting Voosh uses a request **Rate Limiter** to limit the number of requests received by the API within a time frame. Rate Limiter helps maintain system stability during heavy traffic loads. Version: 1.0.0 ## Servers ``` https://growapiservicesv2server.voosh.ai/ ``` ## Security ### apiKey Type: apiKey In: header Name: x-api-key ## Download OpenAPI description [Voosh API Documentation](https://api.voosh.ai/_spec/main.yaml) ## Partner Authentication The Partner Authentication APIs enable Voosh and its partners to securely fetch and manage shared client data. These APIs facilitate seamless integration by providing access to common clients across platforms. ### Key Features: - Retrieve a comprehensive list of restaurant IDs (listing IDs) associated with a client. - Access details of all partner clients within the Voosh system, including their respective locations. - Ensure secure authentication and data retrieval using a unique token ID provided by Voosh. - Maintain accurate client mappings and streamline partner integrations. ### Available APIs: - **Get Intial Access Token API:** Fetches access tokens necessary to authenticate Voosh API's. - **Get Refresh Token API:** Refreshes access tokens. Voosh provides each partner with a unique token ID, which must be included in API requests to authenticate and securely access client data. ### Get Initial Access Tokens - [POST /v1/partnerApi/auth/signin](https://api.voosh.ai/main/partner-authentication/getinitialaccesstokens.md): ## Sign In Endpoint This endpoint is used to authenticate a user and initiate a session by providing the user's credentials. Upon successful authentication, the user receives a token that has a and can be used for subsequent requests. ### HTTP Method ### Request URL #### Request Body | Parameter | Type | Description | | --- | --- | --- | | email | string | The email address of the user. | | password | string | The password for the user. | ### Response The response will indicate the success or failure of the authentication attempt. #### Response Structure | Parameter | Type | Description | | --- | --- | --- | | status | boolean | Indicates if the request was successful. | | statusCode | integer | Code representing the status of the response. | | message | string | A message providing additional information (if any). | | result | object | Contains the authentication result. | | profile | object | User profile information. | | id | string | Unique identifier for the user. | | email | string | Email address of the user. | | username | string | Username of the user. | | token | string | Authentication token for the session (expires in 24 hours). | | refresh | string | Refresh token for obtaining a new access token. | | error | object | Contains error information if authentication fails. | This endpoint allows users to authenticate and sign in to the partner API. ### Refresh Access Tokens - [POST /v1/partnerApi/auth/refresh](https://api.voosh.ai/main/partner-authentication/refreshaccesstokens.md): ## Refresh Token API ### Request URL #### Request Body The request body must be in JSON format and should include the following parameter: | Field | Type | Description | | --- | --- | --- | | refresh | string | The refresh token that is used to obtain a new access token. | : ### Response Upon a successful request, the API returns a JSON response with the following structure: | Field | Type | Description | | --- | --- | --- | | status | boolean | Indicates whether the request was successful. | | statusCode | integer | The status code of the response. | | message | string | A message providing additional information about the response. | | result | object | Contains the result of the request. | | token | string | The newly issued access token. | | error | null or object | Contains error information if any occurred during the request. | : ### Status Codes - : The request was successful, and the token has been refreshed. - Other status codes may indicate different types of errors or issues with the request. This endpoint is essential for maintaining user sessions without requiring frequent logins, enhancing user experience while ensuring security. ## Restaurant Details API **The Restaurant Details API** enables partners to retrieve all restaurant listings associated with **Voosh**, including delivery platform mappings (**DoorDash, Uber Eats, Grubhub**) and store-level availability, grouped by client. There is also support to retrieve specific client restaurant details. This API provides: - **All Restaurant Listings** – Fetches restaurant details for all clients, including listing IDs, restaurant names, and platform-specific store names. - **Platform Availability Flags** – Indicates if each restaurant is listed on DoorDash, Uber Eats, or Grubhub. - **Client-Based Grouping** – Organizes listings under each `clientId` and `clientName` for easier management. ### Get All Restaurant Details - [GET /v1/partnerApi/restaurantDetails/getAllDetails](https://api.voosh.ai/main/restaurant-details-api/getallrestaurantdetails.md): ## Overview This endpoint retrieves detailed information about all restaurants associated with a partner. It provides a comprehensive list of restaurant details, including their active delivery services and listing information. ### HTTP Method ### URL ### Request Parameters This endpoint does not require any request body parameters. ## Response ### Summary The response returns a JSON object containing the status of the request, a message, and the result which includes an array of restaurant details. Each restaurant detail includes information about the restaurant's name, brand, listing ID, and active delivery services. ### Response Fields | Field | Type | Description | | --- | --- | --- | | status | boolean | Indicates if the request was successful. | | statusCode | integer | Code representing the status of the response. | | message | string | Additional information about the request (if any). | | result | object | Contains the details of the restaurants. | | error | object | Contains error information if the request failed. | ### Detailed Breakdown of Result Field #### Result Object The object may contain the following keys: | Field | Type | Description | | --- | --- | --- | | restaurantDetails | array | An array of objects containing details for each restaurant. | #### Restaurant Details Array The object may contain the following keys: | Field | Type | Description | | --- | --- | --- | | clientName | string | The name of the client associated with the restaurant. | | clientId | string | Unique identifier for the client. | | listingDetails | array | An array of objects containing listing information for the restaurant. | ##### Listing Details Array The object may contain the following keys: | Field | Type | Description | | --- | --- | --- | | restaurantName | string | The name of the restaurant. | | brandName | string | The brand associated with the restaurant. | | listingId | string | Unique identifier for the restaurant listing. | | isDoordashActive | boolean | Indicates if the restaurant is active on DoorDash. | | isGrubhubActive | boolean | Indicates if the restaurant is active on Grubhub. | | isUbereatsActive | boolean | Indicates if the restaurant is active on UberEats. | | doordashStoreName | string | The store name used on DoorDash. | | ubereatsStoreName | string | The store name used on UberEats. | | grubhubStoreName | string | The store name used on Grubhub. | ## Example Response This structured documentation provides a clear understanding of the endpoint's purpose, request structure, and response format, enabling users to effectively integrate and utilize the API. ## Reviews API The **Reviews API** enables partners to access, manage, and respond to customer reviews for common clients across multiple platforms. This API provides: - **Reviews Data** – Retrieve detailed reviews submitted by customers across integrated platforms, including ratings, comments, and timestamps. - **Manual Reply to Reviews** – Submit replies manually to individual customer reviews directly through the API. This API helps partners streamline customer engagement, maintain brand reputation, and ensure timely responses to feedback across platforms. ### Get All Order Reviews - [POST /v1/partnerApi/review-manager/reviews](https://api.voosh.ai/main/reviews-api/getallorderreviews.md): # Review Manager API - Fetch Reviews This endpoint allows you to retrieve reviews associated with specific listings within a defined date range. You can specify the number of reviews to return, as well as pagination options. ## Request ### HTTP Method ### URL ### Request Body The request body must be in JSON format and includes the following parameters: | Key | Type | Description | | --- | --- | --- | | startDate | string | The start date for filtering reviews (format: YYYY-MM-DD). | | endDate | string | The end date for filtering reviews (format: YYYY-MM-DD). | | listingIds | array | An array of listing IDs to filter the reviews. | | channel | array | An array specifying the channels from which to fetch reviews (e.g., DOORDASH). | #### Example Request Body ## Response ### Response Body The response will be in JSON format and contains the following structure: | Key | Type | Description | | --- | --- | --- | | status | boolean | Indicates the success of the request. | | statusCode | integer | A code representing the status of the request (0 for success). | | message | string | A message providing additional information about the request. | | result | object | Contains the main data returned from the API. | | error | object | Contains error details if the request was unsuccessful. | #### Result Structure The object may contain the following keys: | Key | Type | Description | | --- | --- | --- | | total | integer | The total number of reviews matching the criteria. | | reviews | array | An array of review objects. | | totalUnAnswered | integer | The total number of unanswered reviews. | | unAnsweredReviews | array | An array of unanswered review objects. | | totalYelp | integer | The total number of Yelp reviews. | | yelpReviews | array | An array of Yelp review objects. | | unansweredYelp | integer | The total number of unanswered Yelp reviews. | | unansweredReviewsYelp | array | An array of unanswered Yelp review objects. | #### Reviews Array Structure Each object in the array contains the following fields: | Key | Type | Description | | --- | --- | --- | | uuid | string | Unique identifier for the review. | | date | string | The date the review was created. | | daysLeftToReply | integer | The number of days left to respond to the review. | | orderSubTotal | number | The subtotal of the order associated with the review. | | CustomerId | string | Unique identifier for the customer who left the review. | | storeId | string | Unique identifier for the store associated with the review. | | brandId | string | Unique identifier for the brand associated with the review. | | deliveryUUID | string | Unique identifier for the order associated with the review. | | toBeReviewed | boolean | Indicates if the review is pending for a response. | | reviewId | string | Unique identifier for the review. | | CustomerName | string | Name of the customer who left the review. | | ListingId | string | Unique identifier for the listing associated with the review. | | channel | string | The channel from which the review originated. | | orderRating | integer | Rating given by the customer for the order. | | reviewReplyPromoValue | number | Promotional value associated with the review reply, if any. | | orderFeedback | string | Feedback provided by the customer regarding the order. | | reviewReplyComment | string | Comment provided in response to the review, if any. | | orderDate | string | The date the order was placed. | | reviewCreated | string | The timestamp when the review was created. | | reviewReplyCreated | string | The timestamp when the review reply was created, if applicable. | | reviewReplied | boolean | Indicates if a reply has been made to the review. | | yelpReplyApproved | boolean | Indicates if the Yelp reply has been approved. | | customerType | string | Type of the customer (e.g., new, returning). | | autoReply | boolean | Indicates if the reply was generated automatically. | #### Example Response ### Status Codes - : The request was successful, and the response contains the requested data. - : Refer to the API documentation for additional status codes and their meanings. This endpoint is essential for managing and analyzing reviews across different channels, helping businesses to respond effectively to customer feedback. ### Reply To Review - [POST /v1/partnerApi/review-manager/reply](https://api.voosh.ai/main/reviews-api/replytoreview.md): ## Review Reply API This endpoint allows partners to submit replies to reviews for their listings. It is designed to facilitate communication with customers by enabling businesses to respond to feedback directly. ## Request ### HTTP Method ### URL ### Request Parameters The request body must be sent in JSON format and includes the following parameters: | Field | Type | Description | | --- | --- | --- | | promoValue | integer | A value representing any promotional offer associated with the reply. | | comment | string | The text of the reply to the customer's review. | | deliveryUUID | string | A unique identifier for the delivery associated with the review. | | customerId | string | The unique identifier of the customer who left the review. | | feedback | string | Any additional feedback that may be relevant. | | listingId | string | The unique identifier of the listing being reviewed. | | rating | integer | The rating given by the customer (scale typically from 1 to 5). | | channel | string | The platform through which the review was received (e.g., DOORDASH). | | customerName | string | The name of the customer who left the review. | | reviewCreated | string | The date when the review was created. | ### Example Request Body ### Expected Response Upon a successful request, the API will return a response with the following structure: | Field | Type | Description | | --- | --- | --- | | status | boolean | Indicates whether the request was successful. | | statusCode | integer | A code representing the status of the response. | | message | string | A message providing additional information about the response. | | result | object | Contains further details about the result of the operation. | | result.message | string | Any relevant message related to the result. | | error | null or object | Will be null if there is no error; otherwise, it will contain error details. | ### Example Response Body ### Notes - A successful request will typically return a 200 status code. - The response structure is consistent across various endpoints of this API, allowing ease of integration and understanding. - Ensure that all required fields are populated correctly to avoid errors in submission. ## Orders API The **Orders API** enables seamless aggregation of order data from multiple third-party platforms for clients common to Voosh and its partners. This API provides: - **Order Details**: Retrieves comprehensive order information from integrated platforms, including order status, timestamps, and itemized breakdowns. - **Financial Insights**: Fetches order-level financial data, offering visibility into revenue, taxes, fees, and other cost components. By consolidating order data across platforms, this API empowers partners to efficiently analyze performance, optimize operations, and ensure accurate financial tracking. ### Get Orders - [GET /orders](https://api.voosh.ai/main/orders-api/getorders.md): The endpoint retrieves a list of orders based on the provided query parameters. The request includes a limit, offset, and clientId to filter the results. Additionally, the request payload includes a start date, end date, listing IDs, and channel to further refine the search. ### Response The response for this request is a JSON object with the following structure: ### Get Order Financials - [GET /orders/financial](https://api.voosh.ai/main/orders-api/getorderfinancials.md): This endpoint retrieves orders with financial details #### Request - Method: GET - URL: {{base-url}}/orders/financial - Query Parameters: - limit (integer, optional): The maximum number of financial orders to retrieve. - offset (integer, optional): The offset for pagination. - clientId (string, required): The unique identifier of the client. - { "startDate": "YYYY-MM-DD", "endDate": "YYYY-MM-DD", "listingIds": \["string"\], "channel": \["string"\] } - startDate (string): The start date for filtering financial orders. - endDate (string): The end date for filtering financial orders. - listingIds (array of strings): The listing IDs to filter financial orders by. - channel (array of strings): The channels to filter financial orders by. #### Response The response is a JSON object with the following schema: ### Get Order Details - [GET /orders/order-details](https://api.voosh.ai/main/orders-api/getorderdetails.md): This endpoint retrieves the details of a specific order based on the provided query parameters. #### Request - Method: GET - URL: {{base-url}}/orders/order-details - Query Parameters: - clientId (string, required): The unique identifier of the client. - deliveryUUID (string, required): The unique identifier of the delivery. - channel (string, required): The channel through which the order was placed. #### Response The response is a JSON object with the following schema: ## Dispute Manager API The **Dispute Manager API** enables partners to track and manage disputed orders for common clients across multiple platforms. This API provides: - **Disputed Order Data**: Retrieves details of disputed orders, including their current status (approved, denied, or expired) and the total number of orders eligible for dispute. - **Dispute Resolution Methods**: 1. **AI Auto Disputes** – Automate the dispute process by enabling AI-powered dispute submission for all locations. 2. **Manual Disputes** – Manually select and submit disputes for specific orders as needed. This API streamlines dispute management, ensuring accurate tracking and efficient resolution of charge discrepancies. ### Get All Disputed Orders - [GET /disputed-manger/orders](https://api.voosh.ai/main/dispute-manager-api/getalldisputedorders.md): This endpoint retrieves disputed orders based on the provided query parameters. #### Request - Method: GET - URL: - Query Parameters: - limit (integer, optional): The maximum number of orders to retrieve. - offset (integer, optional): The offset for paginating through a large result set. - clientId (string, required): The unique identifier of the client. - { "startDate": "YYYY-MM-DD", "endDate": "YYYY-MM-DD", "listingIds": \["string"\], "channel": \["string"\]} - startDate (string): The start date for the order search. - endDate (string): The end date for the order search. - listingIds (array of strings): The IDs of the listings to filter the orders. - channel (array of strings): The channels to filter the orders. #### Response The response for this request can be represented as a JSON schema: ### Get Auto Dispute Configurations - [GET /disputed-manger/auto-dispute/configs](https://api.voosh.ai/main/dispute-manager-api/getautodisputeconfigurations.md): ### Request This endpoint makes an HTTP GET request to retrieve auto-dispute configurations for a specific client. The request should include the client_id as a query parameter in the URL. The last call to this request used the following payload with the raw request body type: ### Response The response will include a status, status code, message, and a result array containing auto-dispute configurations. Each configuration in the result array includes the following details: - id (string): The identifier for the auto-dispute configuration. - channel (string): The channel for which the configuration is applicable. - stores (string): The stores associated with the configuration. - error (string): Any error associated with the configuration. - reason (string): The reason for the dispute. - description (string): Additional description for the configuration. - isActive (integer): Indicates if the configuration is active. - refundPercentage (integer): The refund percentage associated with the configuration. - manuallyCreated (integer): Indicates if the configuration was manually created. - createdAt (string): The date and time when the configuration was created. ### Example Response ### Set Ai Auto Dispute - [POST /disputed-manger/auto-dispute/set-auto-dispute](https://api.voosh.ai/main/dispute-manager-api/setaiautodispute.md): This endpoint allows the user to set an auto dispute for a specific client and channel. #### Request Body - (string) - The channel for which the auto dispute is to be set. - (array) - An array of store IDs for which the auto dispute is to be set. Example: #### Response - (boolean) - Indicates the status of the request. - (integer) - The status code of the response. - (string) - A message related to the response. - (object) - The result of the request. - (boolean) - Indicates the status of the result. - (string) - A message related to the result. - (null) - Indicates any error in the response. Example: ### Raise Manual Dispute - [POST /disputed-manger/manual-raise](https://api.voosh.ai/main/dispute-manager-api/raisemanualdispute.md): This endpoint allows users to manually raise a dispute by providing the delivery UUID, reason for the dispute, and an optional description. - (string): The unique identifier for the delivery. - (string): The reason for raising the dispute. - (string, optional): Additional description for the dispute. - (boolean): Indicates the status of the request. - (integer): The status code of the response. - (string): A message related to the response status. - (object): An object containing the status and message. - (null): Indicates the absence of any error in the response. ### Set Manual Dispute Configurations - [POST /disputed-manger/auto-dispute/manual-config](https://api.voosh.ai/main/dispute-manager-api/setmanualdisputeconfigurations.md): This endpoint allows you to manually configure auto-dispute settings for a specific client. #### Request Body - (string) - The channel for which the dispute configuration is being set. - (string) - The reason for the dispute configuration. - (string) - The error type for which the dispute configuration is being set. - (string) - Additional description for the dispute configuration. - (string) - The specific store(s) for which the dispute configuration is being set. - (string) - The percentage of refund for the dispute configuration. #### Response - (boolean) - Indicates the status of the request. - (integer) - The status code of the response. - (string) - A message related to the status of the request. - (object) - The result of the request, including its status and message. - (null) - Any error message, if applicable. Example Response: ### Get Manual Dispute Config Parameters - [GET /disputed-manger/auto-dispute/get-config-details](https://api.voosh.ai/main/dispute-manager-api/getmanualdisputeconfigparameters.md): This endpoint retrieves the configuration details for auto-dispute functionality based on the provided client ID. #### Request - Method: GET - URL: - Query Parameters: - client_id (string, required): The unique client ID for which the configuration details are requested. #### Response The response will contain the following fields: - (number): The number of listings. - (array): An array of objects containing and . - (array): An array of channels. - (object): An object containing configuration details for different channels such as DOORDASH and UBEREATS. - (object): Configuration details for the DOORDASH channel. - (array): Array of reasons for entirely wrong orders. - (array): Array of reasons for wrong orders. - (array): Array of reasons for ingredient errors. - (array): Array of reasons for incorrect sizes. - (array): Array of reasons for incorrect quantities. - (array): Array of reasons for missing side items. - (object): Configuration details for the UBEREATS channel. - (array): Array of reasons for partially missing items. - (array): Array of reasons for items never received. - (array): Array of miscellaneous reasons. - (array): Array of reasons for missing items. - (array): Array of reasons for wrong orders. - (array): Array of reasons for missing items. - (array): Array of reasons for incomplete orders. - (array): Array of reasons for damaged food. - (string): Additional information. ## Financial Reconciliation API The **Financial Reconciliation API** provides a comprehensive view of financial transactions across multiple locations, enabling accurate tracking and reconciliation of payments, deductions, and discrepancies. This API includes: 1. **Deductions Breakdown** – Retrieve a detailed breakdown of deductions, including commissions, error charges, adjustments, and other fee components. 2. **Estimated vs. Actual Payout** – Access store-wise comparisons between estimated and actual payouts to identify discrepancies. 3. **Tax Bifurcation** – Retrieve store-level tax details, differentiating between taxes remitted to the merchant and those remitted to the state. 4. **POS vs. Third-Party Reconciliation** – Compare POS data with third-party platform records to identify order mismatches, status differences, and unclaimed revenue at the store level. 5. **Deposit Data** – Get store-wise deposit details to track payment settlements and ensure financial accuracy. This API helps partners maintain financial transparency and optimize reconciliation processes across platforms. ### Financial Deduction Breakdown - [GET /finance-manager/financial/overview](https://api.voosh.ai/main/financial-reconciliation-api/financialdeductionbreakdown.md): This endpoint retrieves the financial overview for a specific client. ### Request - Method: GET - Base URL: {{base-url}} - Path: /finance-manager/financial/overview - Query Parameters: - clientId (string, required): The unique identifier of the client for whom the financial overview is being requested. #### Request Body - Type: Raw (JSON) - Description: The request body includes the following parameters: - startDate (string): The start date for the overview. - endDate (string): The end date for the overview. - listingIds (array): An array of listing IDs. - channel (array): An array of channels. - payoutDates (array): An array of payout dates. ### Response - Status: 200 - Content-Type: application/json - Description: The response will be a JSON object with the following schema: ### Store Wise Tax-Details - [GET /finance-manager/financial/tax-details](https://api.voosh.ai/main/financial-reconciliation-api/storewisetaxdetails.md): This endpoint makes an HTTP GET request to retrieve tax details for provide stores(listingIds). The request should include the client ID as a query parameter. The request body should be in raw format and include the start date, end date, listing IDs, channel, and payout dates. ### Request Body - startDate (string): The start date for the tax details. - endDate (string): The end date for the tax details. - listingIds (array): An array of listing IDs. - channel (array): An array of channels. - payoutDates (array): An array of payout dates. #### Example ### Response Upon a successful execution, the endpoint returns a status code of 200 and a JSON response in the format below: The response includes the status, status code, message, and tax details for each store, including the store ID, tax remitted to the state, and tax remitted to the merchant. ### Summary This endpoint retrieves tax details for a specific client based on the provided start date, end date, listing IDs, and channel. The response includes the status, status code, message, and tax details for each store, including the store ID, tax remitted to the state, and tax remitted to the merchant. ### Store Wise Deposit-Details - [GET /finance-manager/financial/deposit-details](https://api.voosh.ai/main/financial-reconciliation-api/storewisedepositdetails.md): This endpoint retrieves deposit details for stores. ### Request - Method: GET - URL: - Query Parameters: - : 604517c0-fae8-41b7-8c20-0fe4778e415c #### Request Body - Type: Raw - { "startDate": "2025-02-23", "endDate": "2025-03-26", "listingIds": \["P5441"\], "channel": \["DOORDASH"\], "payoutDates": \[\]} ### Response - Status: 200 - Content-Type: application/json #### Response Body ### Store Wise Estimted Vs Actual Payout - [GET /finance-manager/financial/estimate-vs-actual-payouts-details](https://api.voosh.ai/main/financial-reconciliation-api/storewiseestimtedvsactualpayout.md): # Financial Estimate vs Actual Payouts Details This endpoint retrieves the financial estimate versus actual payouts details for a specific client. ## Request ### Endpoint ### Query Parameters - (string, required): The unique identifier of the client. ### Request Body - (string): The start date for the financial estimate. - (string): The end date for the financial estimate. - (array of strings): The listing IDs for which the estimate is being calculated. - (array of strings): The channels for which the estimate is being calculated. - (array): The payout dates. ## Response ### JSON Schema The response returns the status of the request, along with the financial estimate versus actual payouts details for the specified client. ### Store Wise POS Vs Off-Premise Details - [GET /finance-manager/financial/pos-vs-off-premise-details](https://api.voosh.ai/main/financial-reconciliation-api/storewiseposvsoffpremisedetails.md): # GET /finance-manager/financial/pos-vs-off-premise-details This endpoint retrieves the details of point of sale (POS) versus off-premise financial data for a specific client. ## Request - Method: GET - Base URL: {{base-url}} - Path: /finance-manager/financial/pos-vs-off-premise-details - Query Parameters: - clientId (string, required): The unique identifier of the client. ### Request Body - Type: Raw - { "startDate": "2025-02-23", "endDate": "2025-03-26", "listingIds": \["P5441"\], "channel": \["DOORDASH"\], "payoutDates": \[\] } ## Response - Status: 200 - Content-Type: application/json - { "status": true, "statusCode": 0, "message": "", "result": { "up_sell": true, "pos": { "name": "", "color": "", "icon": "" }, "is_incomplete": true, "first_date": "", "last_updated": "", "is_pos_available": true, "first_date_off_premise": "", "last_date_off_premise": "", "is_off_premise_available": true, "storeWise": \[ { "storeId": "", "orderDiff": { "offPremise": 0, "pos": 0, "missedOffPremise": 0, "missedPos": 0, "totalMissedOrders": 0 }, "subTotalDiff": { "pos": 0, "offPremise": 0, "diffOffPremise": 0, "diffPos": 0, "totalDiff": 0 }, "statusDifference": { "totalDiff": 0 }, "revenueToClaimBack": 0 } \] }, "error": null }