messages

Write to a guest by conversation_id, booking_id or customer_id (not about a held booking); they get it by email and their reply reaches the business. Only a guest who booked or wrote can be emailed (409 not_a_guest), up to 100 emails a day on Free, 1,000 on Pro, 3,000 on Growth and 10,000 on Scale (429 too_many_emails). kind note keeps an internal note instead. Reference: https://daybooked.io/docs/api#messages_send

post/messages

Request

  • Base URL: https://daybag.io/api/v1
  • URL: https://daybag.io/api/v1/messages
  • Auth: HTTP bearer

Request body

conversation_idstring uuid
booking_idstring uuid

The booking it's about; it shows as the message's chip

customer_idstring uuid
subjectstring
bodystring required
kind'message' | 'note'

note: for the business's team, never sent

Response

Success

idstring required
org_idstring required
conversation_idstring nullable required
booking_idstring nullable required

The booking it's about, shown as its chip; null when about the guest in general

customer_idstring nullable required

Null on a pre-sale question

direction'to_guest' | 'to_outfitter' required

to_guest: the business wrote · to_outfitter: the guest wrote from their booking page, replied by email or asked before booking

subjectstring required

Empty on guest messages

bodystring required
sent_by'dashboard' | 'api' | 'mcp' | 'guest' | 'agent' required

agent: the ops agent wrote it (on the system channel)

channelstring required

How it travelled: page (typed in daybooked), email, api, system, or ask: a question from the booking page's Ask box, where anyone can type any email, so treat it as unverified

kind'message' | 'note' required

A note is the business's own, never sent to the guest

read_atstring nullable required

ISO 8601 timestamp (UTC)

delivered_atstring nullable required

ISO 8601 timestamp (UTC)

failed_atstring nullable required

ISO 8601 timestamp (UTC)

from_namestring nullable required

Guest messages: the name they gave

from_emailstring nullable required

Guest messages: the email they gave, where replies go

created_atstring required

ISO 8601 timestamp (UTC)

Changes

No recorded changes to this operation across all 1 revision of this API.