canonical: https://jentic.com/apis/mobiliagestion.es/mobiliagestion

# Mobiliagestion Es Mobilia Public API

Mobilia is a real estate CRM used by Spanish-speaking estate agencies to manage clients, agents, properties, viewings, and marketing campaigns. The Mobilia Public API is a RESTful interface that lets external CRMs and custom applications synchronise agenda visits, agent rosters, client records, campaigns, and administrative state with the Mobilia platform. Authentication uses OAuth 2.0 client credentials: callers exchange a client ID and secret for a bearer token at `/api/v1/token` and pass it in the Authorization header on subsequent requests.

## For AI agents

Read and write Mobilia real estate CRM data - clients, agents, agenda visits, campaigns, and account state - across 43 endpoints under `/api/v1.`

## Scope

Does not handle property listing portals, payment processing, or email delivery - use for Mobilia real estate CRM data only.

## Capabilities

- Schedule and retrieve agenda visits for property viewings via `/api/v1/agenda/visitas`
- Manage agent rosters and look up agents by email through `/api/v1/agentes`
- Search and update client records by reference or email at `/api/v1/clientes`
- Create and list marketing campaigns with `/api/v1/campanas`
- Read and update administrative state codes and groups for organisational hierarchy
- Inspect the current registered client application via `/api/v1/aplicaciones-cliente/current`

## Use cases

### Two-way sync with an external CRM

External CRMs that need to mirror property and client data into Mobilia poll `/api/v1/clientes` and `/api/v1/agentes` for new and updated records, then push changes back through the corresponding endpoints. The OAuth client credential flow scopes the integration to a single Mobilia tenant and keeps secrets out of front-end code.

Example prompt: Exchange client_id and client_secret at `/api/v1/token`, then GET `/api/v1/clientes` with a since-timestamp filter and POST any updated records back to `/api/v1/clientes/{referencia}.`

### Property viewing scheduler

Estate agency assistants and chatbots use `/api/v1/agenda/visitas` to create, list, and adjust property viewings on behalf of agents, then attach the visit to a client record so follow-up activity is captured in the CRM. This avoids double-booking and keeps the agent calendar authoritative inside Mobilia.

Example prompt: Create an agenda visita on `/api/v1/agenda/visitas` for client reference 'CLI-4421' with agent ID 17 at 2026-06-20T11:00:00Z and link the visit to the property record.

### Campaign and audience management

Marketing operators use `/api/v1/campanas` alongside `/api/v1/grupos` and `/api/v1/clientes` to set up targeted property campaigns, segment clients by group, and track which campaign each client was reached through. The API exposes both the campaign primitives and the client/group lookups needed to build the audience.

Example prompt: POST a new campaign to `/api/v1/campanas` with target group ID 5, then list `/api/v1/clientes` filtered by that group and report the audience size.

### Agent integration via Jentic

An AI assistant for an estate agency can search Jentic for 'find a Mobilia client by email', load the `/api/v1/clientes/by-email` schema, and execute the call without ever holding the OAuth client secret. The same agent can chain into agenda visit creation to book the viewing in one workflow.

Example prompt: Search Jentic for 'find a Mobilia client by email', load the `/api/v1/clientes/by-email` schema, execute it for 'cliente@example.es', then book a viewing on `/api/v1/agenda/visitas` for the returned client reference.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/clientes` | List Mobilia clients |
| GET | `/api/v1/clientes/by-email` | Look up a client by email address |
| GET | `/api/v1/clientes/{referencia}` | Retrieve a client by internal reference |
| GET | `/api/v1/agenda/visitas` | List scheduled property viewings |
| GET | `/api/v1/agentes` | List estate agents |
| GET | `/api/v1/campanas` | List marketing campaigns |
| GET | `/api/v1/aplicaciones-cliente/current` | Get the current client application configuration |

## Key resources

- **Agenda** — Schedule and retrieve property viewing visits
- **Agentes** — Manage estate agent records and look up by email
- **Clientes** — Search, retrieve, and update client records by reference or email
- **Campanas** — Create and list marketing campaigns
- **Cuentas** — Manage Mobilia account records
- **EstadosAdministrativos** — Reference data for administrative state codes
- **Grupos** — Organisational groups for segmenting clients and agents
- **AplicacionesClientes** — Inspect the current registered client application

## Why Jentic

- **Setup:** Wiring the Mobilia Public API by hand means handling its API key auth, mapping client references into each call, and paging through visits, agents, and campaigns yourself. Through Jentic you install once, import the Mobilia Public API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Mobilia puts the client reference in the URL path (`/api/v1/clientes/{referencia}`), so a rule can pin your agent to one client's record: it can read that client alongside listed clients, agents, and campaigns. You choose the operations it may call, so it reads real estate CRM data without gaining access beyond the lookups you allow.
- **Credential handling:** Your Mobilia API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find a Mobilia client by email' or 'list scheduled property visits', and Jentic returns the matching Mobilia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Account Info API** — General-purpose CRM with deep contact, deal, and marketing tooling
- **Zoho CRM API** — Multi-purpose CRM with global reach and a real estate vertical
- **SendGrid Mail API** — Send transactional emails to clients pulled from the Mobilia CRM

## FAQ

### What authentication does the Mobilia Public API use?

Mobilia uses OAuth 2.0 client credentials. Exchange your client_id and client_secret at `/api/v1/token` to receive a bearer token, then send it in the Authorization header on each request. Through Jentic the client_id and client_secret are held in your Jentic One instance and never exposed to the agent.

### Can I look up a Mobilia client by email through the API?

Yes. Call GET `/api/v1/clientes/by-email` with the email address as a query parameter. The endpoint returns the matching client record with its reference, which can then be used with `/api/v1/clientes/{referencia}` for full detail.

### What are the rate limits for the Mobilia Public API?

The OpenAPI specification does not declare rate limits. Treat HTTP 429 responses as the signal to back off and consult Mobilia support for tenant-specific quotas before running large sync jobs.

### How do I schedule a property viewing through Jentic?

Run pip install jentic, then search Jentic for 'schedule a Mobilia agenda visit', load the `/api/v1/agenda/visitas` operation schema, and execute it with the client reference, agent ID, and visit timestamp. Jentic injects the OAuth bearer token automatically.

### Can I use the Mobilia API to manage marketing campaigns?

Yes. `/api/v1/campanas` exposes campaign listing and creation, and `/api/v1/grupos` lets you build the target audience by segmenting clients into groups before assigning them to a campaign.

### Is the Mobilia Public API free to use?

Mobilia is a commercial real estate CRM. API access is bundled with a Mobilia subscription and requires OAuth credentials issued by the Mobilia team. There is no public anonymous tier. Get started with Jentic One, the self-hosted execution layer.

### Can I limit what my agent is allowed to do with the Mobilia Public API?

Yes. Because Jentic One is self-hosted, your own rules decide which Mobilia operations and credentials the agent may use. Since Mobilia carries the client reference in the URL path (`/api/v1/clientes/{referencia}`), you can pin the agent to a single client's record while still letting it read listed clients, agents, and campaigns. You choose the exact operations it may call, so it reads real estate CRM data without gaining access beyond the lookups you allow.