Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
Switch to light modeSwitch to dark mode
APIs / CRM / Mobilia Public API
Mobilia Public API logo

Mobiliagestion Es Mobilia Public API

Official vendor OpenAPI document · agent-readyCRMContact 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.

Use for: I need to schedule a property viewing in the Mobilia CRM, Find a Mobilia client record by email, List all agents working in a specific Mobilia office, Retrieve a Mobilia client by their internal reference

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

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.

Jentic One on GithubView OpenAPI Document

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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmobiliagestion.es%2Fmobiliagestion" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmobiliagestion.es%2Fmobiliagestion" | 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

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

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

GET

/api/v1/campanas

List marketing campaigns

GET

/api/v1/aplicaciones-cliente/current

Get the current client application configuration

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

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

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 management

Credential isolation

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.

Intent-based discovery

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot Account Info API

→

General-purpose CRM with deep contact, deal, and marketing tooling

Choose HubSpot when the agency wants a general CRM with strong marketing automation; choose Mobilia for Spanish real estate-specific workflows like property viewings.

Alternative

Zoho CRM API

→

Multi-purpose CRM with global reach and a real estate vertical

Use Zoho CRM when the agency operates outside Spain or wants Zoho's broader product suite; use Mobilia for tenants already on Mobilia.

Complementary

SendGrid Mail API

→

Send transactional emails to clients pulled from the Mobilia CRM

Pair SendGrid with Mobilia when the agent needs to email clients or agents fetched from /api/v1/clientes - Mobilia does not deliver email itself.

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

GET STARTED

Start building with Mobilia Public API

Explore with Jentic One
View OpenAPI Document