Etna Real Estate publishes a public, read-only API and an MCP server through which AI assistants and developers fetch real data about properties, categories, services, articles and the agency itself on the Omiš Riviera. No registration or key is required, a plain HTTP GET on /api/v1 is enough.
When to use this API
The API is the right choice when:
- you need real, currently available property in Omiš and on the Omiš Riviera, not placeholder content
- you want the agency contact details or the service list to cite in an answer
- you are building an integration that must stay compatible within v1
The API is not meant for bookings, reservations or payments: every route is read-only, and enquiries go through the form at /en/contact.
Authentication and limits
The API is public. No route requires a key, a token or OAuth; an integration that asks for credentials is misconfigured.
- Rate limit: 60 requests per minute per IP address. The remaining count is returned in RateLimit-* headers.
- Locale: the locale parameter accepts hr, en or de (default hr). Slugs differ per language, so send identifiers as a slug in the locale you asked for, or as a numeric id.
- Pagination: per_page accepts 1 to 50, default 20. The meta object returns page, per_page, total and last_page.
- Errors: returned as application/problem+json following RFC 9457, with type, title, status and detail.
- Versioning: every route lives under /api/v1. Removing a route is announced with Deprecation and Sunset headers at least 90 days in advance.
Endpoints
Nine public routes, all GET. The full description of each route, its response schema and its error codes live in the OpenAPI document.
| Method | Path | Description |
|---|---|---|
GET |
/api/v1/agency |
Name, address, phone, email, opening hours, area served and languages of the agency. |
GET |
/api/v1/properties |
Property list with category, place, service, price_from, price_to, surface_from, surface_to and q filters. |
GET |
/api/v1/properties/{property} |
A single property by numeric id or slug, with description, price, surface and gallery. |
GET |
/api/v1/categories |
Property categories with the number of listings in each. |
GET |
/api/v1/categories/{category} |
A single category by slug, whichever locale the slug was sent in. |
GET |
/api/v1/services |
Agency services: sale and purchase brokerage, valuation, mortgage paperwork. |
GET |
/api/v1/posts |
Blog articles with title, summary, publication date and link. |
GET |
/api/v1/posts/{post} |
A single article by slug or id, with the full text. |
GET |
/api/v1/pages |
Static pages such as About us, with title and content. |
Example request
Fetching a single property in English. The response carries the properties in data, plus meta and links for pagination.
Request
curl "https://www.etna-realestate.com/api/v1/properties?locale=en&per_page=1"
Response (truncated)
{
"data": [
{
"id": 9,
"slug": "building-land-with-panoramic-sea-view",
"title": "BUILDING LAND WITH PANORAMIC SEA VIEW",
"url": "https://www.etna-realestate.com/lands/building-land-with-panoramic-sea-view",
"category": { "slug": "lands", "title": "Lands" },
"place": "OMIŠ",
"surface_m2": 7000,
"price": { "amount": 400, "currency": "EUR", "formatted": "400 €" },
"featured": true
}
],
"meta": { "page": 1, "per_page": 1, "total": 51, "last_page": 51 },
"links": { "self": "…?page=1", "next": "…?page=2", "prev": null }
}
The url field is always an absolute link to the property page. Do not build slugs yourself, use the returned url.
MCP server
The same data is also available through a Model Context Protocol server at /mcp (JSON-RPC 2.0, Streamable HTTP transport). The server exposes the tools get_agency_info, search_properties, get_property, list_categories and get_article, plus resources with the agency profile and an agent guide.
GET /mcp returns a JSON description of the server, so availability can be checked with a plain request.
Machine-readable documents
Everything needed for automatic discovery is published at predictable addresses:
- https://www.etna-realestate.com/openapi.json — OpenAPI 3.1 description of every route, parameter and response schema.
- https://www.etna-realestate.com/auth.md — What requires authentication and what does not, plus the limits.
- https://www.etna-realestate.com/en/llms.txt — Agency summary and page index for language models.
- https://www.etna-realestate.com/llm-info.json — Agency details in JSON, for machine reading.
- https://www.etna-realestate.com/.well-known/mcp/server-card.json — MCP server card: protocol, transport, tools and resources.
- https://www.etna-realestate.com/.well-known/api-catalog — Linkset (RFC 9727) with the API and MCP entry points.
- https://www.etna-realestate.com/.well-known/agent-skills/index.json — Agent skills index with the file checksums.
Contact
Questions about the API, notice of a larger crawl, or a bug report: office@etna-realestate.com, +385 98 891 838.