API access is available on Enterprise plans only. API keys are created and issued by homie — you cannot generate them yourself. Contact your homie account team to request access.
Authentication
Every request must include your API key in thex-api-key header. Keys are issued to your organization by homie — keep them secret and use them only from server-side code.
The chat flow
A typical integration follows three steps:1
Create a chat
Call Create Chat with your
chatbotId. You receive a chatId that identifies the conversation.2
Add a message
Call Add Message with the
chatId, the user’s message, and the currentUrl. The assistant starts generating a response.3
Listen to events
Open the Message Events stream for the
chatId to receive the assistant’s reply and tool activity in real time over Server-Sent Events.Error format
Errors return a non-2xx HTTP status and a JSON body with amessage describing what went wrong:
API usage counts toward your plan’s monthly message quota. When the quota is reached, message endpoints return an error until it resets or your plan is upgraded. Monitor consumption under Usage on the platform.
Pagination
List endpoints return a paginated envelope. Theitems array holds the results for the current page, and the remaining fields describe the overall set:
prevPage and nextPage are null when there is no previous or next page.
Identifiers
All resource IDs (chatId, chatbotId, userId, organizationId) are unique string identifiers, for example 5e9c1a2b-3d4e-4f60-b2f2-9f4b1c2d3e4f.
Endpoints
Create Chat
Start a new conversation for a chatbot.
Get Chat
Retrieve a chat by its ID.
Add Message
Send a user message to the assistant.
List Messages
Page through a chat’s message history.
Message Events
Stream assistant responses over SSE.
PDP Question Set
Fetch public product questions for a page.