Apex27 API

Name: Apex27 API
Brand: Apex27 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey85 EndpointsREST

For Agents

Manage estate agent contacts, listings, leads, viewings, offers, and tenancies in the Apex27 CRM via an X-Api-Key.

Install Jentic One Beta

Connect the Apex27 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apex27 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 Apex27 API.

Manage contacts and contact orders, including referrals, call logs, and free-form notes

List and update property listings, branches, and the agents that own them

Capture leads from marketing sites and route them into the right Apex27 branch

GET STARTED

Start building with Apex27 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Apex27 API for, with concrete tasks.

★ Lead capture from marketing sites

Pipe new buyer or tenant enquiries from a marketing site into the Apex27 CRM so the right agent at the right branch picks them up. The agent posts contact details to /contacts (creating or matching), records the originating listing as a referral on /contacts/{contactId}/referrals, and adds a context note via /contacts/{contactId}/notes.

POST a contact to /contacts (or fetch existing by phone), POST the source listing to /contacts/{contactId}/referrals, and POST an enquiry note to /contacts/{contactId}/notes

Viewing and offer workflow

Run the full viewing-to-offer workflow from outside the Apex27 UI. The agent schedules viewings against listings, captures the verbal offer, and logs it back to the property so the negotiator sees a clean trail. Useful for agencies that take initial calls in a contact-centre tool and want the trail to land in Apex27.

Schedule a viewing for a listing, then once a verbal offer is received, POST the offer record and notify the negotiator

Tenancy lifecycle for letting agents

Manage the full tenancy lifecycle for letting agents: from initial enquiry (contact, viewing, offer) through to active tenancy and inspections. The agent calls /tenancies endpoints to advance state and /inspections to record property condition reports. This keeps a single source of truth for the property's history.

Advance a tenancy from offer to active and POST a move-in inspection record with the agent and timestamp

Client portal sign-in flow

Generate a one-click sign-in URL for an applicant or landlord so they can log into the agency's Apex27 portal without a password reset round-trip. The agent calls /client-portal/log-in-url or /client-portal/sign-in-url for the contact, then sends the URL via email or SMS through a separate channel.

POST /client-portal/sign-in-url for the contact and email the returned URL via the agency's mail provider

AI agent integration via Jentic

An agent supporting an Apex27-using agency can search Jentic for 'create a contact' or 'capture a lead' and Jentic returns the matching Apex27 operation. The X-Api-Key is held in the Jentic vault so the agent never handles the secret, and the 85-endpoint surface is reachable through one search-load-execute pattern.

Search Jentic for 'create a contact in Apex27', load the /contacts schema, and POST a new contact record

Key Endpoints

85 endpoints — jentic publishes the only available openapi specification for apex27 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/contacts

List contacts in the CRM

GET

/contacts/{id}

Fetch a single contact by id

GET

/contacts/{contactId}/call-logs

List call logs for a contact

GET

/contacts/{contactId}/notes

List notes against a contact

POST

/client-portal/authenticate

Authenticate a client portal user

POST

/client-portal/sign-in-url

Generate a one-click portal sign-in URL

GET

/branches

List branches in the agency

GET

/contacts

List contacts in the CRM

GET

/contacts/{id}

Fetch a single contact by id

GET

/contacts/{contactId}/call-logs

List call logs for a contact

GET

/contacts/{contactId}/notes

List notes against a contact

POST

/client-portal/authenticate

Authenticate a client portal user

Why Jentic?

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

Credential isolation

Apex27 X-Api-Key values are stored encrypted in the Jentic vault (MAXsystem). The header is attached server-side per call, so the agent context never holds the agency's API key.

Intent-based discovery

Agents search Jentic by intent ('create a contact', 'schedule a viewing', 'log an offer', 'generate a portal sign-in URL') and Jentic returns the right Apex27 operation among the 85 available with its parameter schema.

Time to first call

Direct integration: 1-3 days to map contacts, listings, viewings, offers, and the client-portal flow. Through Jentic: under an hour for any individual operation - search, load, execute.

FAQs

Specific to using Apex27 API through Jentic.

Why is there no official OpenAPI spec for Apex27 API?

Apex27 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Apex27 API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Apex27 API use?

API key auth in the X-Api-Key header, issued from the agency's Apex27 admin area. Through Jentic the key is held in the encrypted MAXsystem vault and attached server-side per call, so the secret never enters the agent context or the URL.

Can I capture a website lead and route it to a branch through this API?

Yes. POST a contact to /contacts (or fetch existing), POST the source listing as a referral on /contacts/{contactId}/referrals, and add a note via /contacts/{contactId}/notes. Branch routing is driven by the listing's branch which is returned in the listing record.

How do I generate a client portal sign-in URL through Jentic?

Search Jentic for 'generate an Apex27 portal sign-in URL', load the schema for /client-portal/sign-in-url, and execute it for the contact. The returned URL is single-use and can be sent to the applicant via the agency's normal email or SMS channel.

What are the rate limits for the Apex27 API?

Apex27 applies per-key rate limits that are not declared in the OpenAPI spec. In practice agency-tier keys are sized for normal interactive use; high-volume integrations should batch reads with pagination rather than tight loops.

Does Apex27 support webhooks for new contacts and viewings?

Yes. Apex27 exposes webhook registration endpoints so an external system can be notified when listings, contacts, or viewings change, instead of polling. Register the target URL and Apex27 POSTs change events to it.

Apex27 API

Connect the Apex27 API to your agent

Capabilities

Start building with Apex27 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs