Fousレストランボード
Get your Restaurant Board bookings through an API
Read the 予約リスト (reservation list), new and cancelled bookings in 予約受付管理 and your 顧客台帳 (customer ledger) from Restaurant Board with one API call each. Or have a workflow email you the day's 要連絡 (to contact) and 仮予約 (provisional) bookings before opening.
Works with your own レストランボード account. Fous is an independent product.
What you can build on Restaurant Board
Get the reservation list
Build thisReads the 予約リスト (reservation list) for a date or date range, with each booking's status, visit time, guest, party size, table and course.
- Takes
- Store, start date, end date, status (optional), exclude cancellations (optional)
- Returns
- Status, visit time, last name, first name, party size, phone, table, course, keyword, notes, memo
Check new, changed and cancelled bookings
Build thisReads the 予約受付管理 (booking intake) screen: bookings received, changed or cancelled, listed by 受付日時 (received at), with who took them.
- Takes
- Store, 受付状況 (新規, 変更, キャンセル or すべて)
- Returns
- Received at, 予約状況, staff, visit date and time, guest name, party size, table
Search the customer ledger
Build thisRuns 詳細検索 (detailed search) on the 顧客台帳 (customer ledger) by birth month, visit count, last visit date or other conditions.
- Takes
- Store, birth month, visit count, last visit from and to, registered from and to (all optional)
- Returns
- Customer number, name, gender, birth month, phone, email, visit count, last visit date
Register a reservation
Build thisOpens 予約登録 (new booking), picks the date, time, party size and table, enters the guest's details and registers the booking.
- Takes
- Store, date, time, party size, table (optional), guest name, phone, course (optional), memo (optional)
- Returns
- Status, visit date and time, guest name, party size, table, any overlap message
Automate Restaurant Board with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
Bookings to call back, before opening
Build this- Starts
- Every day at 10:00, Asia/Tokyo
- Step 1
- For each store you name, get today's 予約リスト with cancellations excluded.
- Step 2
- Keep the bookings in 要連絡 or 仮予約 status.
- Step 3
- Email you the list per store, with time, name, party size and phone number.
New cancellations, posted to the team channel
Build this- Starts
- Every 30 minutes
- Step 1
- For each store, read 予約受付管理 with 受付状況 set to キャンセル.
- Step 2
- Keep the cancellations that were not there on the last run.
- Step 3
- Post each one, with visit date, time, name, party size and table, to your Slack webhook.
Next month's birthdays from the customer ledger
Build this- Starts
- Monthly on the 20th at 9:00, Asia/Tokyo
- Step 1
- For each store, search the 顧客台帳 for customers whose 誕生月 is next month.
- Step 2
- Keep the ones with a 前回来店日 in the last 12 months.
- Step 3
- Post name, phone, email, visit count and last visit date to your CRM webhook.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the reservation list” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "restaurant-board.com/get_reservation_list",
"input": {
"store": "Northwind Dining",
"start_date": "2026-11-13",
"end_date": "2026-11-13",
"exclude_cancellations": true
}
}'
{
"status": "completed",
"data": {
"store": "Northwind Dining",
"count": 1,
"reservations": [
{
"status": "来店待ち",
"visit_time": "18:00",
"last_name": "山田",
"first_name": "花子",
"party_size": 4,
"phone": "090-0000-1234",
"table": "T3",
"course": "季節のコース",
"keyword": "記念日",
"notes": "誕生日プレート",
"memo": "窓側希望"
}
]
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
Restaurant Board’s own options
Recruit's pages for Restaurant Board describe no public API. It connects to Recruit's own services: Hot Pepper Gourmet bookings and seat inventory, reservation emails from other gourmet sites, and Airレジ or selected POS registers. The base features cost 0 yen with no limit on accounts.
| Option | What it covers | What it takes |
|---|---|---|
| ホットペッパーグルメ連携 (Hot Pepper Gourmet link) | Hot Pepper Gourmet net bookings appear in the ledger automatically, and seat inventory is shared with Hot Pepper Gourmet. | A store listed on Hot Pepper Gourmet, linked to Restaurant Board. |
| グルメサイトメール取り込み (gourmet-site email import) | Reads reservation emails from sites such as ぐるなび, 食べログ and Retty into the ledger. | The Hot Pepper Gourmet link, and the 取り込み専用メールアドレス set in each site's store admin. |
| Airレジ and POSレジ連携 (register link) | Airレジ adds checkout data to the 顧客台帳. With a supported POS register, its table slips sync to show seat status. | Airレジ, or a contract for Airレジ オーダー モバイルオーダー 店内版 for POSレジ and a supported POS register. |
| Restaurant Board by hand | The 予約リスト, スケジュール, テーブル管理, 顧客台帳 and 集計分析 screens. The reservation list prints or sends as a PDF. | A free account (基本機能利用 0円), signed in with an AirID. |
Read on November 12, 2026: レストランボード 機能, レストランボード 費用, グルメサイトメール取り込み画面について.
Signing in to Restaurant Board
Restaurant Board signs you in with your AirID or email address and a password. If you have turned on 2段階認証 (two-step sign-in), it asks for a code from an authenticator app or by SMS, and a multi-store account picks the store after signing in. With Fous you sign in once through Restaurant Board's own sign-in with your own account, and the login is sealed with AES-256.
Worth knowing
- A business day runs from 05:00 to 29:00
- The 予約リスト takes 05:00 to 29:00 (05:00 the next morning) as one day, so a 1:00 booking belongs to the previous date. Booking times are chosen between 05:00 and 28:55.
- 予約受付管理 shows the last 7 days
- 予約受付管理 leaves out walk-ins (直接来店), bookings already 来店済み or 退店, and bookings 7 days or more past. On the PC version the screen is for stores listed on Hot Pepper Gourmet.
- Some fields need the Hot Pepper Gourmet link
- 予約依頼番号, ポイント, 予約種別, the guest's ご要望事項 and 手書きメモ appear only for stores listed on Hot Pepper Gourmet. グルメサイトメール取り込み needs the link too.
- One login, several stores
- An account that manages several stores is shown a store selection screen after signing in, so each method you build takes the store as an input.
More in Food service, restaurants and alcohol
- SGWS Proof
- Provi
- myCoke
- BEES
- METRO Online-Kundenkonto
- Sligro
- Deliveroo Partner Hub
- DoorDash Merchant Portal
- foodpanda Partner Portal
- Glovo Manager Portal
- GrabMerchant
- Grubhub for Restaurants
- iFood Portal do Parceiro
- Just Eat Partner Hub
- PedidosYa Partner Portal
- Rappi Aliados
- Swiggy Partner
- Uber Eats Manager
- Wolt Merchant Portal
- Zomato Restaurant Partner
- 饿了么商家版
- 배민셀프서비스
- Gordon Ordering
- PFG CustomerFirst
- Sysco Shop
- US Foods MOXē
- Bidfood Direct
- Brakes
- Transgourmet Webshop
- OpenTable GuestCenter
- TheFork Manager
- Restaurant365
- 食べログ店舗管理画面
- Oracle MICROS Simphony Reporting & Analytics
- Toast Web
- Insights C3M
Other industries: YONO Business, CareCredit Provider Center, RD e-Filing, TRACES, Viator Supplier Center, DIAN MUISCA.
Frequently asked questions
Not a public one: Recruit's pages describe no API. Restaurant Board connects to Hot Pepper Gourmet, imports reservation emails from other gourmet sites, and links with Airレジ and selected POS registers. Fous builds a method on top of your own account instead.
The help centre describes printing the 予約リスト, or sending it as a PDF, from its その他 menu. With Fous, a method returns the same list as JSON for the dates you choose, and a workflow can email it to you or post it to your own system.
Yes, when グルメサイトメール取り込み is set up and the store is linked to Hot Pepper Gourmet. You enter Restaurant Board's 取り込み専用メールアドレス in each site's store admin, and 予約受付管理 shows those bookings with 自動取込 as 担当.
Yes. One AirID can manage several stores, chosen after signing in. A workflow can loop over the stores you name, call the same method for each and send you one summary by email or webhook.
No. Fous is an independent product. You use it with your own Restaurant Board account, and a method reads and does only what that account can.
Put レストランボード behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextOpenTable GuestCenterTheFork ManagerRestaurant365YONO BusinessHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of レストランボード (Recruit). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.