Menu Push
vGrubs calls you{your_base_url}/merchants/menuvGrubs calls this endpoint to push the full menu for a merchant. Your system should replace the existing menu for that merchant with the data provided.
vGrubs pushes the menu automatically after a successful integration connection: the connect call responds first and the menu webhook follows about 2 seconds later, so you can save the store on your side before it arrives. Additionally, vGrubs may call this endpoint at any time when a menu correction or update is made on our side. If the push never arrives, request a fresh one with Publish Menu.
The menu is structured around four core entities - categories, items, modifier groups, and options - which reference each other via id. Availability schedules are defined separately and linked to categories.
Request body
The partner's store ID.
The full menu for the merchant, structured around the entities below.
Reference
categories└── items[] ──────────────────► items└── availability ─────────────────► availabilitiesitems└── modifiers[] ──────────────────► modifierGroups└── options[] ──────────► options└── modifiers[] ──► modifierGroups (nested)
Responses
Whether the menu was received and applied successfully.
Missing or invalid fields in the request body.
Invalid or missing API key.