Grubhub · Schema
PosAccountStatus
The current state of the merchant with regards to work flow and how they are conducting business.
Food DeliveryRestaurantMarketplaceOnline OrderingPoint-of-SaleLogisticsLast Mile DeliveryMenu ManagementHospitalityLocal CommerceDelivery
Properties
| Name | Type | Description |
|---|---|---|
| merchant_status | string | The merchant's current status concerning account creation or ability to receive orders in a machine-readable format |
| merchant_status_descriptor | string | The merchant's current status concerning account creation or ability to receive orders in a human-readable format |
| pos_merchant_status | string | The merchant's current status concerning account creation or ability to receive orders (online/offline) |
| reason | string | Reason explaining why the merchant has a given status |
| holds_active_account | boolean | Whether or not this merchant should be regarded as holding an active account with GrubHub |
| accepting_phone_orders | boolean | Whether or not this merchant is currently capable of receiving orders by phone |
| accepting_online_orders | boolean | Whether or not this merchant is currently capable of receiving orders that have been transmitted online |
| merchant_status_comments | string | The reason that this merchant is in the status it is in, typically reserved for merchants not conducting business |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/grubhub/main/json-schema/grubhub-posaccountstatus-schema.json",
"title": "PosAccountStatus",
"x-generated": "2026-09-17",
"x-method": "derived",
"x-source": "openapi/grubhub-merchant-data-openapi.yml#/components/schemas/PosAccountStatus",
"type": "object",
"properties": {
"merchant_status": {
"type": "string",
"description": "The merchant's current status concerning account creation or ability to receive orders in a machine-readable format",
"deprecated": true
},
"merchant_status_descriptor": {
"type": "string",
"description": "The merchant's current status concerning account creation or ability to receive orders in a human-readable format",
"deprecated": true
},
"pos_merchant_status": {
"type": "string",
"description": "The merchant's current status concerning account creation or ability to receive orders (online/offline)"
},
"reason": {
"type": "string",
"description": "Reason explaining why the merchant has a given status"
},
"holds_active_account": {
"type": "boolean",
"description": "Whether or not this merchant should be regarded as holding an active account with GrubHub"
},
"accepting_phone_orders": {
"type": "boolean",
"description": "Whether or not this merchant is currently capable of receiving orders by phone",
"deprecated": true
},
"accepting_online_orders": {
"type": "boolean",
"description": "Whether or not this merchant is currently capable of receiving orders that have been transmitted online",
"deprecated": true
},
"merchant_status_comments": {
"type": "string",
"description": "The reason that this merchant is in the status it is in, typically reserved for merchants not conducting business"
}
},
"description": "The current state of the merchant with regards to work flow and how they are conducting business."
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/grubhub-posaccountstatus"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
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.