Grabbly API

Name: Grabbly API API
Brand: Grabbly API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey2 EndpointsREST

For Agents

Browse available restaurants and place a food order on behalf of a user. Two endpoints cover discovery and order submission.

Quickstart

Get started with Grabbly API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"place a food delivery order with grabbly"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Grabbly API API.

List available restaurants on the Grabbly marketplace via GET /restaurants

Place a food order against a Grabbly restaurant through POST /orders

Submit order line items as part of the POST /orders body

Authenticate through the Authorization header using a Grabbly-issued API key

GET STARTED

Start building with Grabbly API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Grabbly API API for, with concrete tasks.

★ Conversational Food Ordering Agent

A chat assistant takes 'order me dinner' and walks through GET /restaurants to surface options, then POST /orders to submit the user's chosen items. The published surface is intentionally narrow — there is no menu, modifier, or order-tracking endpoint in the spec — so the agent must work within that scope and ask the user for explicit item details.

Call GET /restaurants, present the list to the user, then POST /orders with the chosen restaurant and item array.

Restaurant Discovery for Local Apps

Local lifestyle and concierge apps query GET /restaurants to populate a 'food nearby' tab without operating their own restaurant database. Refresh on user open or on demand to keep the list current. The endpoint does not include menus or pricing, so apps that need item-level information must fetch that elsewhere.

Call GET /restaurants on app launch and render the response into a card list with the restaurant name and id for downstream order calls.

Voice Assistant Reorder Flow

A voice assistant remembering 'usual order' presents the saved restaurant and items, confirms with the user, and submits POST /orders in one shot. The Grabbly spec does not include a saved-order primitive, so the assistant stores the prior order locally and re-uses the captured restaurant id and item payload to reconstruct the request.

Replay a stored Grabbly order by issuing POST /orders with the cached restaurant_id and items array after voice confirmation.

Agent-Driven Ordering via Jentic

An AI assistant picks up a request like 'order pizza for tonight' and uses Jentic to discover Grabbly's two endpoints. The agent calls /restaurants for options, then /orders to submit. The Authorization API key is held in Jentic's vault, so the agent never handles the raw secret.

Use the Jentic SDK to search 'place a food order', load POST /orders, and execute with the chosen restaurant_id and items list.

Key Endpoints

2 endpoints — grabbly is a food delivery and restaurant marketplace api.

METHOD

PATH

DESCRIPTION

GET

/restaurants

List available restaurants on the Grabbly marketplace

POST

/orders

Place a food order against a chosen restaurant

GET

/restaurants

List available restaurants on the Grabbly marketplace

POST

/orders

Place a food order against a chosen restaurant

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Grabbly's Authorization API key is stored in Jentic's MAXsystem vault. The header is injected at execution time, so the agent never sees the raw key in prompts, transcripts, or tool outputs.

Intent-based discovery

Agents search Jentic with intents like 'place a food order' and Jentic surfaces POST /orders with its body schema, so the agent does not have to model the order shape from scratch.

Time to first call

Direct integration: a couple of hours given the small surface, plus partner onboarding time. Through Jentic: under 15 minutes once the API key is in the vault.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Toast POS API

Restaurant POS platform pairing with marketplaces for kitchen-side fulfilment

Use Toast on the restaurant side when Grabbly is the consumer-facing marketplace; the two cover different parts of the order pipeline.

Alternative

Shopify Admin API

Hosted commerce platform for restaurants selling beyond delivery marketplaces

Pick Shopify when the merchant wants their own branded online ordering store rather than appearing inside a marketplace like Grabbly.

Complementary

Square API

Payments and POS that complement marketplace order capture

Use Square for the in-store payment and POS layer when Grabbly handles delivery orders and you need a consolidated ledger.

FAQs

Specific to using Grabbly API API through Jentic.

What authentication does the Grabbly API use?

Grabbly uses an API key sent in the Authorization header (security scheme name 'apiKey'). Generate the key in your Grabbly account and send it on every request. Through Jentic, the key is stored in MAXsystem and injected into Authorization at execution time so the agent never sees it.

Can I retrieve restaurant menus with this API?

The published OpenAPI spec only exposes GET /restaurants and POST /orders. There is no menu, modifier, or item-pricing endpoint. Agents must obtain item details out-of-band — for example from a partner agreement with the restaurant — before submitting an order body.

What are the rate limits for the Grabbly API?

The OpenAPI spec does not declare rate limits. Limits are enforced at the Grabbly gateway tied to the Authorization key. Cache the /restaurants response for short windows since the list does not change frequently within a session.

How do I place an order through Jentic?

Search Jentic for 'place a food order', load POST /orders, and execute with a restaurant_id plus items array. The Jentic SDK returns the order confirmation payload so the agent can quote the order id and any returned status back to the user.

Can I track an order's delivery status with this API?

The current spec does not expose an order-tracking endpoint. Order tracking, if available, is handled outside this OpenAPI surface. For now, the agent should treat the POST /orders response as the canonical confirmation and prompt the user to track via the Grabbly app or notifications.