Respond to Peerspace booking requests before they expire

1. Peerspace sends an email or a text for each new booking request with the booking details and your expected payout; text alerts need a verified phone number under the Profile tab.
2. Open the request from the link in that notification or from your Peerspace bookings page, and read the date, hours, attendees, activity and add-ons.
3. Open the Calendar tab in the top menu and toggle to the right space, because pending inquiries and requests show there for you but stay available to other guests.
4. Accept, decline or message the guest. When the price or hours on the request are wrong, Peerspace tells hosts to send an invite-to-book with the corrected details instead.
5. Every request repeats this within two business days. The one that arrives on a weekend, or the second request for an already requested slot, is the one that slips.

Go through my pending Peerspace booking requests, oldest deadline first. Accept the ones on free slots with 30 people or fewer, ask the guest when the activity is unclear, and show me anything that clashes.

1. 01

   Work the deadlines, not the inbox order

   The agent pulls every pending request with list_bookings and sorts by expires_at. Anything due within 24 hours is handled first, and a request that already expired is listed for you, since nothing can be done on it.

2. 02

   Read the request against your rules

   get_booking gives the activity, headcount, add-ons and expected payout. The agent compares them with the limits you set in the prompt (headcount, no amplified music, no open flames) and holds any request that breaks one.

3. 03

   Look for clashes on that space

   get_calendar for the request day shows confirmed bookings and other pending requests. An overlap with a confirmed booking is a clash. Two pending requests for the same hours are both put in front of you, because the agent does not pick a winner by arrival time.

4. 04

   Accept only the clean ones

   A free slot inside your rules goes to accept_booking_request, after your OK unless you switched confirmation off. The agent reminds you that accepting charges the guest in full, so a request with a doubtful activity is never accepted to save the deadline.

5. 05

   Answer the rest before the clock runs out

   When the activity or headcount is unclear, the agent asks the guest one specific question with send_message, which Peerspace counts as a response. A clash on a date you cannot offer becomes decline_booking_request plus a short message that names the nearest free day.

4 pending requests on Daylight loft studio.
Accepted after your OK: Dana, Fri 17 Oct 14:00 to 18:00, photo shoot, 12 people, payout $477.
Asked: Marcus, Sat 18 Oct, "birthday gathering" for 35 people; asked whether music will be amplified (expires Tue 09:12).
Clash: Priya and Leo both requested Sun 19 Oct 10:00 to 14:00. Pick one; the other gets a decline with Sun 26 Oct offered.
Expired before this run: 1 request from Jordan, Wed 8 Oct.

• A Peerspace booking request expires after two business days without an accept or decline, and Peerspace warns that many expired requests can lead to removal from the platform.
• Peerspace counts a message to the guest, an accept or a decline as a response, so a question in the thread protects the response rate while the decision waits.
• Peerspace response rate is the share of inquiries and requests answered within 24 hours, and Power Host eligibility starts at 90%.
• Accepting a Peerspace request charges the guest in full, and the payout goes by ACH to the host's bank account within 7 days after the reservation ends.
• Peerspace buffer time (30 minutes, 1 hour or 2 hours, set per space from the Calendar) applies only to new requests, so requests already pending keep the buffer they were made with.

accept_booking_request, decline_booking_request and send_message ask for your OK by default. To run it daily without you, switch confirmation off for those tools in your dashboard.

Sources: Peerspace help: What happens when I receive a booking request? · Peerspace help: Why shouldn't I let booking requests expire? · Peerspace help: What is my response time and response rate? · Peerspace help: How to incorporate a buffer time in between bookings

curl https://cotlet.dev/api/v1/peerspace/accept_booking_request \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"booking_id":"b_90417"}'

{
  "booking_id": "b_90417",
  "status": "confirmed",
  "start": "2026-10-17T14:00:00-07:00",
  "end": "2026-10-17T18:00:00-07:00",
  "total": 530
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is peerspace_accept_booking_request. Example data.

• Answer Peerspace inquiries with your real availability and rules
• Send a Peerspace custom offer (invite to book) from an inquiry
• Peerspace API and MCP server: every tool
• All use cases