PROD

Returns the lightweight list of all your published properties, in a single call and without the 20 cap of properties, to generate your site's sitemap.xml.

It includes the properties of the networks your account is connected to with website publishing: the same ones your site shows.

Resource information
AuthenticationRequired (API Token, Bearer)
Scopeexpress-base
HTTP MethodGET
ResponseJSON
Version1

Resource URL

https://mapaprop.app/api/action/express-v1/properties/sitemap

Parameters

None. The account is resolved from the token, it is not sent as a parameter.

Sample code

GET /api/action/express-v1/properties/sitemap HTTP/1.1
Host: mapaprop.app
Authorization: Bearer {access_token}

Response

A JSON array with one object per property, sorted by last update date descending.

FieldTypeDescription
seoUrlstringThe property's friendly URL, with no leading slash and no domain
codestringThe property code
lastUpdatestringLast update date, in ISO 8601 format. This is what goes into the sitemap's <lastmod>
propertyIdintegerThe property's internal id
customerIdintegerThe account that owns the property. It may not be yours: on a property that arrives through a network, the owner is the other customer

Sample response

[
    {
        "seoUrl": "venta-de-departamento-en-agronomia-capital-federal-1-2617750",
        "code": "1-IMP-1789518927056",
        "lastUpdate": "2026-10-20T10:34:01.000-03:00",
        "propertyId": 2617750,
        "customerId": 1
    }
]

If your account has no published properties, the response is an empty array.

To build the link to each property use seoUrl: it is the identifier this service returns. If your site routes by seoUrl —like the sites Mapaprop hosts— that is enough. If your site opens the listing with the hash, keep in mind this service does not return it, and the hash is only available from GET /api/action/express-v1/properties.

If the inventory were too large to be served complete in one response, the service returns an error instead of a truncated list. This is deliberate: an incomplete sitemap tells the search engine those pages do not exist, which is worse than having no sitemap.