Homito developer platform

Build with Homito.

Integrate properties, listings and application flows. Start with one authenticated read.

Make your first API call →Connect an agent →

A REST API origin is configured. A verified public MCP installation is not currently offered by this reference.

First request

Start with a single request.

A clear path from company access to your first integration.

Get company access
An administrator creates a key with the permissions your system needs.
Make your first read
Run the server example and check the HTTP response.
Build your integration
Continue with deliberate writes, synchronization and webhooks.

Server example

curl

curl --proto '=https' --fail --silent --show-error --connect-timeout 5 --max-time 10 \
  --output /dev/null --write-out 'HTTP %{http_code}\n' \
  "$HOMITO_API_BASE_URL/api/v1/landlord/inventory/properties?limit=1" \
  -H "Authorization: Bearer $HOMITO_API_KEY"

Prepare your server environment

Ask a company administrator for a key with read:properties. Set HOMITO_API_BASE_URL to the configured HTTPS API origin, without a path or query. Inject HOMITO_API_KEY from your server secret manager; never put it in browser code, a URL or an agent conversation.

Example behavior and limits

These SDK-free server examples make the same first read. curl and JavaScript use a 10-second total deadline. Python uses a 10-second blocking network timeout, not a total-response deadline. JavaScript and Python reject responses over 2 MiB and print only count/hasMore; curl discards the body and prints HTTP status. Save the JavaScript example as first-read.mjs and run it with Node.js 20 or later.

Build with Homito.

Start with a single request.

Explore integration guides

Getting started

Build and integrate

Operate and support