---
title: "Order Rejected"
method: POST
path: "/orders/{id}/reject"
tags: ["Order API Order Platform Webhooks"]
---

# Order Rejected

`POST /orders/{id}/reject`

The Order Reject endpoint enables the order platform to mark an order as rejected. This action can be triggered by various scenarios, such as when a restaurant manually rejects an order, the system automatically rejects an order due to mapping issues, or if items in the order are out of stock. This endpoint ensures that rejected orders are properly recorded and communicated to both the restaurant and the customer.

## Path parameters

- `id` string, required

## Request body

- OrderRejection — Order rejection information
  - `reason` 'OUT_OF_ITEMS' | 'INVALID_ITEMS' | 'OTHER', required — Order cancellation reasons
  - `note` string — Reason or note for rejection
  - `timestamp` string, date-time, required — Order rejection time

## Response `204`

Successful response OK

## Other responses

- `400` — Bad request
- `404` — Resource not found
- `500` — Internal server error

---

[API](https://skmtc.net/grubtech/apis/grubtech-auth-server.md) · [All operations](https://skmtc.net/grubtech/apis/grubtech-auth-server/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/grubtech/grubtech-auth-server/revisions/21688b6dcb69/schema)