R2 Connect API
Orders
Every commercial transaction of the business, from any vertical: lodging, restaurant, store and experiences.
GET/ordersrequires read:orders
GET/orders/{order_number}requires read:orders
Same fields as reservations, but without filtering by vertical. This is the right resource for accounting: a hotel with a restaurant generates both types and both must be recorded.
Parameters#
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Results per page. Between 1 and 50. Default: 25. |
| cursor | string | Cursor for the next page, taken from pagination.cursor. |
| created_from | date | Start date, format YYYY-MM-DD (UTC) or epoch milliseconds. |
| created_to | date | End date, inclusive. Same format. |
| status | string | Filter by exact status. |
| Parameter | Type | Description |
|---|---|---|
| type | string | Filter by order type. Available on this resource only. |
Order types#
| Value | What it represents |
|---|---|
booking | Lodging reservation. |
space_booking | Booking of a space rented by the hour. |
dine_in | On-premise consumption. |
command | Restaurant order ticket. |
takeout · pickup | Takeout or pickup. |
delivery | Delivery. |
room_service | Room service. |
Example#
bash
# All orders in July
curl -H "Authorization: Bearer YOUR_KEY" \
"https://api.r2-os.com/api/connect/v1/orders?created_from=2026-07-01&created_to=2026-07-31&limit=50"
# Restaurant tickets only, already completed
curl -H "Authorization: Bearer YOUR_KEY" \
"https://api.r2-os.com/api/connect/v1/orders?type=command&status=completed"