Every published listing is stored in our database under its Id. You can eventually unpublish it (Zonaprop API > DELETE aviso ), republish it (Zonaprop API > PUT aviso ) or modify it without losing the data.
This web service is used to obtain the Navent access token from the credentials.
Replaced on June 18, 2025 by the new internal function Zonaprop API > ZonapropAuth() Private Doc
| Type | Description |
|---|---|
| Authorization | Property API authorization token |
Production
| Resource information | |
|---|---|
| Authentication | Required |
| HTTP Method | POST |
| Response | JSON |
| Version | 1 |
Resource URL
https://api-navent.mapaprop.com/property-api/navent/login
Parameters - JSON Body
| Name | Type | Required | Description |
|---|---|---|---|
| clientId | string | yes | The client credentials id |
| clientSecret | string | yes | The client credentials secret id |
Example Body
// example body
{
clientId: "UserNavent",
clientSecret: "123456789"
Response
A JSON indicating the listing status
| Object | Field | Type | Description |
|---|---|---|---|
| Response | success | string | The JSON of the access credentials |
| error | string | A text indicating where the error occurred |
Sample code
//Authorization required
//METHOD POST
//Endpoint
https://api-navent.mapaprop.com/property-api/navent/login
Once we receive a response like this, our listing will be ONLINE:
{
access_token: '{REDACTED-EXAMPLE-TOKEN}',
token_type: 'bearer',
expires_in: 315262766,
scope: 'read write trust'
}