0%
SnapListly

SnapListly API

Draft specification · homelist.imetroll.com · public endpoints are not open in this release

Agencies that already run listing software can attach SnapListly instead of building their own vision pipeline. Photos go in. A structured listing draft comes back.

1. Purpose

The API is meant to turn property room photos into JSON: rooms, short descriptions, tags and an MLS-style overview. The same draft the web workspace shows after Analyze.

2. Who it is for

Broker platforms, agency CRMs and mobile apps that already store listings. Not for anonymous public scraping. An account on SnapListly LLC is required.

3. Auth

A later release will issue a server-side key per account. The key stays on the agency server. It is never placed in a public web page or a mobile binary.

4. Send photos

Planned call: HTTPS POST multipart field photos[] to an endpoint under homelist.imetroll.com. Same limits as the workspace: up to 40 images, about 12 MB each. JPEG or PNG.

POST /analyze.php
Content-Type: multipart/form-data
photos[] = file
lang = pl

5. Response JSON

The body is JSON. Typical keys: rooms[].name, rooms[].description, overallDescription, tags[]. The web app already consumes this shape.

6. Language

Send a language code (one of the 48 UI languages). The model prompt stays in English. Room names, overview and tags come back in that language.

7. Limits and tokens

The first three analyses on a new account are free. Further calls use the account token balance. Apple and Google collect payment. SnapListly LLC does not store card numbers.

8. Status of this version

This page is the product description. The public partner API is not enabled yet. The workspace POST on analyze.php is the same pipeline and requires a logged-in session. Partner keys will be issued after billing is live.

SnapListly LLC · office@homelist.imetroll.com