Mobiliagestion Es Mobilia Public API

Name: Mobilia Public API
Brand: Mobilia Public API
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey43 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Mobilia Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mobilia Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mobilia Public API.

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

GET STARTED

Start building with Mobilia Public API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Mobilia Public API for, with concrete tasks.

★ 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.

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.

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.

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.

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

43 endpoints — mobilia is a real estate crm used by spanish-speaking estate agencies to manage clients, agents, properties, viewings, and marketing campaigns.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Mobilia OAuth 2.0 client_id and client_secret are stored in the Jentic MAXsystem vault. Agents receive scoped bearer tokens issued by /api/v1/token; raw secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent — 'find a Mobilia client by email', 'schedule a property viewing', 'list Mobilia campaigns' — and Jentic returns the matching /api/v1 operation with its input schema.

Time to first call

Direct Mobilia integration: 2-4 days to wire OAuth, model the /api/v1 surface, and handle pagination across 43 endpoints. Through Jentic: under 1 hour for first call once credentials are vaulted.

FAQs

Specific to using Mobilia Public API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up.