Argenprop

Argenprop is one of the portals PropertyAPI publishes to. It has no endpoints of its own: you use the same methods as for any other portal, passing argenpropapi where the route asks for {portal}.

PUT    /property-v1/properties/{paId}/publication/argenpropapi
GET    /property-v1/properties/{paId}/publication/argenpropapi
DELETE /property-v1/properties/{paId}/publication/argenpropapi

Publishing to Argenprop is not available yet through this API: today you can declare the client, connect their account and verify their properties, and the verifier already tells you, listing by listing, whether it would go out on Argenprop. The three routes above answer 400 until it is enabled.

That means you can have your integration ready — and your clients' connections already made — before the portal is enabled. Write to dev@mapaprop.com if you want us to let you know.

Where to start


1 · Declare the client	Clients — the agency's record, once per client
2 · Connect their account	Connect with a link — your client types their integration credential on a page of ours; you never see it
3 · Load the property	Creating properties · Verify first
4 · Publish	⏳ not yet — see the note above

What is specific to Argenprop

It works with POINTS, not with plans

This is the underlying difference from the other portals, and it explains almost everything else.

	How it works
Other portals	your client buys N listings or a plan, and each listing consumes one
Argenprop	your client buys a subscription with a number of points and splits them across their listings to position them: more points on a listing, better position

What this means for your integration:

The points balance cannot be queried through the API. It is visible in Argenprop's panel. That is why, in the client's record, the plans and quota fields for argenpropapi always come back null: it is not that we cannot read them, it is that the portal does not expose them.
The balance is discovered when you publish. If your client ran out of points, the listing is not created and we tell you with the portal's own reason.
The subscription is handled with Argenprop, not with us: buying it, renewing it and cancelling it are matters between your client and the portal.

Argentina-based agencies only

Argenprop operates only in Argentina, and integration credentials are handed out to Argentine agencies. If your client is not from Argentina, this portal does not apply — see Publication for the ones that do.

The credential is not the one for their portal account

Argenprop hands out separate integration credentials by email: a username in the format xxx@api.com, a password, and a number the email calls IdAnunciante — and also IdVendedor: they are the same thing.

If your client types the email and password they use to sign in to the Argenprop site, the connection is registered and publications then fail on permissions. The connection page warns them about it; if you see that error reported, the first thing to check is which username they connected with.

Your client types them on our connection page — you never see them and we do not store the password — and what gets stored is the permission the portal returns. Details: Connect with a link.

On connecting, the portal may take down the previous CRM's listings

If your client had been publishing on Argenprop through another channel — the portal's own panel or another CRM — Argenprop may take those listings down when the account moves to being managed from a new system. It is the portal's policy to avoid duplicate listings when things are republished, and Argenprop is the one who does it: it is not something Mapaprop or your integration does.

Let your client know before connecting, and plan on republishing their portfolio from your system once they are connected.

And the flip side: the portal advises against managing the same account through two channels at once (its panel and your integration) — it produces drift and duplicate listings. What is expected is that, once connected, everything is managed from a single place.

Which fields of its own it accepts in `publication`

Field	What it is
`advertiserId`	The agency's identifier on the portal
`visible`	Whether the listing is published visible

What each one means and how to send it: the publication key.

Zones are not mapped through the API. We maintain the your-zone → Argenprop-zone mappings; you send your zone and we resolve the rest. If a zone is not mapped, the verifier tells you before you publish. The location catalogues are in Zones.

PropertyAPI — the index of the whole API
Publication — the available portals and what sets them apart
Zonaprop — the other portal with a section of its own