Nekst API
★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey30 EndpointsREST
For Agents
Manage real estate transactions, contacts, tasks, and roles in Nekst, and subscribe to webhooks that fire when deal milestones change.
Use for: Create a new real estate transaction in Nekst from a signed contract, List all open transactions assigned to a specific agent, Update the status of a transaction when escrow closes, Subscribe to a webhook that fires whenever a transaction status changes
Not supported: Does not handle MLS listings, document signing, or commission disbursement — use for real estate transaction tracking only.
Jentic publishes the only available OpenAPI specification for Nekst API, keeping it validated and agent-ready. Nekst is a real estate transaction management platform that automates the post-contract checklist for agents and brokerages, turning repetitive closing steps into scheduled tasks, reminders, and assigned activities. The API exposes transactions, contacts, tasks, webhooks, and roles so external systems can sync deal data, read transaction status, and react to contract milestones. It is designed for real estate teams that want to integrate Nekst with their CRM, MLS feed, or document workflow.
Install Jentic One Beta
Connect the Nekst API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nekst 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 instanceJentic 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 Nekst API.
Create and update real estate transactions with status, role assignments, and milestone dates
Sync contact records between Nekst and an external CRM using the contacts endpoint
Subscribe to webhooks that fire when a transaction status changes so agents are notified instantly
Read and assign roles across a transaction including buyer, seller, lender, and title officer
Pull a complete transaction history for reporting, commission calculation, or compliance review
Verify API token validity through the auth test endpoint before running scheduled jobs
Use Cases
Patterns agents use Nekst API for, with concrete tasks.
★ Real Estate Transaction Sync
Brokerages running a separate CRM or document platform use the Nekst API to keep transaction data in lockstep. The /v1/transactions endpoints expose create, read, and status update operations, so a contract signed in DocuSign can spawn a Nekst transaction with the right role assignments in seconds rather than hours of manual entry.
Create a new transaction in Nekst with property address 123 Main St, status Under Contract, and assign roles for buyer agent and listing agent.
Milestone Webhook Notifications
Operations teams subscribe to Nekst webhooks so downstream systems react when a transaction status flips. The /v1/webhooks endpoints register a callback URL, and /v1/transactions/{id}/status drives the events. This replaces email parsing or polling loops and lets a Slack channel or commission engine update the moment escrow closes.
Register a webhook pointing at https://example.com/nekst-events and verify it fires when a transaction status changes to Closed.
Contact and Role Management
Transaction coordinators use the contacts and roles endpoints to assemble the cast for each deal — buyers, sellers, lenders, inspectors, and title agents. The API reads the role catalogue from /v1/roles and writes contact links via /v1/contacts, removing the duplicate-entry problem when a contact already exists in the firm CRM.
List the available roles in Nekst, then attach an existing buyer contact to transaction id 4711 with the role Buyer.
AI Agent Integration via Jentic
An AI agent loads Nekst operations through Jentic by searching for the intent rather than reading docs. Jentic returns the matching operation schema, the agent fills in property address, role assignments, and milestone dates, and executes the call against /v1/transactions without ever touching the raw API token.
Use Jentic to search for create real estate transaction, load the schema, and create a Nekst transaction tied to a contract signed today.
Key Endpoints
30 endpoints — jentic publishes the only available openapi specification for nekst api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v1/auth/test
Verify the API token is valid
GET
/v1/transactions
List transactions
GET
/v1/transactions/{id}
Get a single transaction
PUT
/v1/transactions/{id}/status
Update a transaction status
GET
/v1/contacts
List contacts
GET
/v1/webhooks
List registered webhooks
POST
/v1/webhooks
Register a webhook
GET
/v1/roles
List role definitions
GET
/v1/auth/test
Verify the API token is valid
GET
/v1/transactions
List transactions
GET
/v1/transactions/{id}
Get a single transaction
PUT
/v1/transactions/{id}/status
Update a transaction status
GET
/v1/contacts
List contacts
GET
/v1/webhooks
List registered webhooks
POST
/v1/webhooks
Register a webhook
GET
/v1/roles
List role definitions
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Nekst API token is stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access at execution time and the raw token never enters the agent context.
Intent-based discovery
Agents search Jentic by intent (for example, create a real estate transaction) and Jentic returns the matching Nekst operation with its input schema, so the agent can call the right endpoint without reading the docs.
Time to first call
Direct Nekst integration: 1-2 days for token handling, webhook setup, and error retries. Through Jentic: under 1 hour to search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
HubSpot CRM
General-purpose CRM that pairs with Nekst to hold the wider contact and deal record
Choose HubSpot when the agent needs to write a contact or deal into the firm-wide CRM after a Nekst transaction is created.
FAQs
Specific to using Nekst API through Jentic.
Why is there no official OpenAPI spec for Nekst API?
Nekst does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nekst 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 Nekst API use?
The Nekst API uses an API token sent via the apiToken security scheme. Jentic stores the token encrypted in the MAXsystem vault and injects it at execution time, so the token never enters the agent context. You can verify the token by calling GET /v1/auth/test.
Can I subscribe to transaction status changes with the Nekst API?
Yes. Register a webhook with POST /v1/webhooks and point it at your callback URL. Nekst will POST to that URL when a transaction status changes, including the events surfaced by /v1/transactions/{id}/status.
How do I create a real estate transaction with the Nekst API through Jentic?
Search Jentic for create real estate transaction, load the operation schema for POST /v1/transactions, then execute with the property and role payload. The full flow is pip install jentic, search, load, execute.
What are the rate limits for the Nekst API?
Nekst does not document explicit per-second rate limits in the spec. Treat the API as a regular write-light, read-moderate service: cache role and contact lookups, and avoid polling /v1/transactions when a webhook subscription will deliver the same change events.
Can I list all the role types available in a Nekst transaction?
Yes. Call GET /v1/roles to get the full catalogue of role definitions, which you then reference when attaching contacts to a transaction via /v1/contacts.
GET STARTED