Tableo Restaurant API
Bookings

Check In Booking

Check in (arrive) a booking. The booking must be in a status that allows the check-in transition (typically confirmed or accepted).

POST
/api/restaurant/bookings/{booking}/check-in

Authorization

bearerAuth
AuthorizationBearer <token>

Supports two token types:

  1. Restaurant tokens — API tokens with restaurant-api ability, issued per restaurant.
  2. User tokens — Personal access tokens with mobile-access ability (e.g. for the mobile app). When managing multiple restaurants, include X-Restaurant-Id: <id> header.

In: header

Path Parameters

booking*string

Booking ID or reference string.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://devrms.tabdevx.com/api/restaurant/bookings/string/check-in"
{
  "message": "Booking checked in successfully",
  "booking": {
    "id": 123,
    "reference": "API-ABC123",
    "status": "arrived_in_service"
  }
}
{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  },
  "meta": {
    "timestamp": "2019-08-24T14:15:22Z"
  }
}
{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  },
  "meta": {
    "timestamp": "2019-08-24T14:15:22Z"
  }
}

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Booking not found.",
    "details": null
  },
  "meta": {
    "timestamp": "2026-03-18T10:00:00Z"
  }
}

{
  "message": "Booking cannot be cancelled in its current status",
  "current_status": "cancelled"
}

{
  "error": {
    "code": "string",
    "message": "string",
    "details": {}
  },
  "meta": {
    "timestamp": "2019-08-24T14:15:22Z"
  }
}