get_event_booking_status
Scenes (Events & Shows): Check the status of an event ticket booking after payment is confirmed. Call this after check_payment_status reports a successful terminal payment. Returns the final booking details: venue, date, time, guest count, and order ID.
Required: orderId (from place_event_order response).
See get_event_booking_status in actionComing soon
Usage notes
- Use this after payment succeeds, or when a free booking came back as still processing.
- The booking details are returned under
bookingrather thandata.
Example
const result = await client.callTool({
name: "get_event_booking_status",
arguments: {
orderId: "ord_42",
},
});Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
orderId | string | yes | Order ID from the booking confirmation. |
Session credentials (user identity, access token) are supplied automatically by the authenticated MCP session - you do not pass them in the tool call. See Authenticate.
Response
All Swiggy MCP tools return:
{
"success": true,
"data": { /* tool-specific payload */ },
"message": "optional human-readable message"
}
On failure:
{
"success": false,
"error": { "message": "description of what went wrong" }
}
See Error codes for the full catalogue.
Output schema
booking: {
orderId: string;
restaurantId: string;
restaurantName: string;
restaurantLocation?: string;
reservationDate: string;
reservationTime: string;
guestCount: number;
dealTitle: string;
status: string;
bill?: {
subTotal: number;
totalBillAmount: number;
charges: Array<{ name: string; totalCost: number }>;
taxes: Array<{ name: string; totalCost: number }>;
discounts: Array<{ name: string; totalCost: number }>;
};
}
This tool returns the confirmation under booking rather than data, so clients that read only data will see nothing. Read booking for the venue, date, time, guest count, and bill breakdown.
Schema notes
- The confirmation is returned under
booking, notdata. status: aPROCESSINGvalue means the booking is not final yet. Wait and check again rather than reporting it as confirmed.bill: itemised amounts for the booking, when the service provides them.restaurantName/restaurantLocation: the venue hosting the show.reservationDate,reservationTime, andguestCountare the show date, show time, and ticket count.orderId: order identifier for tracking and support. Preserve formatting exactly as returned.- Fields marked optional may be omitted depending on user state, cart/order state, and live Swiggy availability.
- Use returned identifiers and enum values exactly as provided; do not invent fallback IDs, status values, payment methods, or timestamps.
Details
| Field | Value |
|---|---|
| Name | get_event_booking_status |
| MCP Server | Scenes |
| Endpoint | POST mcp.swiggy.com/scenes |
| Stage | Booking |
| Behaviour | read-only |