BoomTown API

Name: BoomTown API API
Brand: BoomTown API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey, oauth2142 EndpointsREST

For Agents

Manage real-estate CRM contacts, log calls and texts, run drip plans, and react to lead lifecycle webhooks across BoomTown's 142 endpoints.

Quickstart

Get started with BoomTown API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a BoomTown real estate contact"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BoomTown API API.

Create, search, and update real-estate contacts with addresses, phone numbers, and email records

Log calls, texts, notes, and special dates against a contact's timeline

Assign, pause, resume, and terminate drip plans for nurturing leads

Manage todos and tasks for agents and contacts within an organization

GET STARTED

Start building with BoomTown API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BoomTown API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BoomTown API, keeping it validated and agent-ready. BoomTown is a real-estate CRM and lead management platform that helps brokerages capture, nurture, and convert prospect leads into closed transactions. The API exposes contacts, communications, todos, transactions, drip plans, and webhooks so agents and integrations can read and update lead records, log calls and texts, manage assigned tasks, and react to lifecycle events. It uses OAuth 2.0 for user authorization plus an x-api-key header derived from the client_id and client_secret hash.

Use Cases

Patterns agents use BoomTown API API for, with concrete tasks.

★ Sync website leads into BoomTown for follow-up

Brokerages pipe leads from their IDX website, paid ad campaigns, and partner portals into BoomTown so every prospect lands in one CRM with assigned ownership and a drip plan. The API accepts new contacts via POST /contacts, attaches phone, email, and address records, and assigns a drip plan in the same flow. Most brokerages launch the integration in a few days using the OAuth flow and webhook subscriptions.

Create a contact for buyer Jane Doe with email jane@example.com and phone +14155550100, then assign drip plan id dp_42 and confirm the assignment id

Outbound call and text logging from a softphone

Agents make and receive calls and texts in a separate softphone or texting tool, but managers want every interaction logged on the contact's BoomTown timeline for compliance and reporting. The API offers POST /contacts/{contactId}/callLogs and read endpoints for /texts so a middleware service can post call summaries and pull text history without forcing agents to copy-paste. Setup typically takes a sprint.

Append a call log to contact id ct_12345 with duration 240 seconds, outcome 'left voicemail', and the agent user id usr_77

Drip-plan automation for new buyer leads

Marketing teams run lifecycle drip campaigns that pause when a lead replies and resume after qualification. The API exposes assignedDripPlans endpoints to pause, resume, terminate, and list active plans on a contact, which lets an agent or rules engine react to inbound replies without leaving the BoomTown environment. Drip orchestration typically replaces manual list management within the first week.

Pause the drip plan with id adp_999 on contact ct_12345, then resume it after the agent has confirmed qualification

Transaction pipeline reporting

Operations leaders need a live view of transactions across the brokerage by status to forecast revenue and spot stuck deals. POST /organizations/{tenantId}/transactions/search and the matching aggregate/status endpoint return filtered transaction lists and counts per status, ready to feed a BI dashboard or weekly stand-up report.

Search transactions for tenant org_abc with status 'pending' updated in the last 30 days and aggregate the results by status

Agent-driven lead triage via Jentic

An AI agent triages new BoomTown registrations from a webhook, pulls the contact's recent communications, and decides whether to assign a drip plan or escalate to a human agent. Through Jentic the agent searches for 'find a BoomTown contact' and 'assign a drip plan', loads the schemas, and executes the calls without ever holding the OAuth refresh token in its context.

Search Jentic for 'assign a BoomTown drip plan', load the schema, and execute it against contact ct_55555 with drip plan id dp_buyer_warm

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/contacts

Create a new contact

GET

/contacts/{contactId}

Retrieve a contact by id

POST

/contacts/textSearch

Full-text search across contacts

POST

/contacts/{contactId}/callLogs

Log a call to a contact's timeline

POST

/contacts/{contactId}/assignedDripPlans

Assign a drip plan to a contact

POST

/organizations/{tenantId}/transactions/search

Search transactions across the organization

POST

/webhooks/events/contactUpdated

Subscribe to the contactUpdated webhook

POST

/oauth2/token

Exchange an authorization code for an access token

POST

/contacts

Create a new contact

GET

/contacts/{contactId}

Retrieve a contact by id

POST

/contacts/textSearch

Full-text search across contacts

POST

/contacts/{contactId}/callLogs

Log a call to a contact's timeline

POST

/contacts/{contactId}/assignedDripPlans

Assign a drip plan to a contact

Why though Jentic?

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

Credential isolation

BoomTown's OAuth refresh token and x-api-key are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access — raw refresh tokens and client secrets never enter the agent's prompt or logs.

Intent-based discovery

Agents search Jentic for intents like 'log a call in BoomTown' or 'assign a drip plan' and Jentic returns the matching operations with their input schemas, so the agent calls the right endpoint without crawling the BoomTown docs.

Time to first call

Direct BoomTown integration: 1-2 weeks for OAuth, webhook handshakes, and drip plan logic. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Real Geeks API

Real-estate IDX website plus CRM aimed at the same brokerage segment as BoomTown.

Choose Real Geeks when the brokerage already runs the Real Geeks IDX website and wants tightly coupled lead capture; choose BoomTown for richer drip and transaction tooling.

Alternative

HubSpot CRM Contacts API

General-purpose CRM with contact management; not real-estate specific.

Use HubSpot CRM when the team needs cross-industry CRM features and marketing hub integration; use BoomTown when real-estate transactions and drip plans are the priority.

Alternative

Pipedrive API

Sales-pipeline CRM with deal stages but without real-estate transaction primitives.

Choose Pipedrive for generic sales pipelines; choose BoomTown when contacts, transactions, and lifecycle webhooks need to be real-estate aware.

Complementary

HubSpot Webhooks API

Webhooks bus often used to fan BoomTown events out to other downstream tools.

Pair HubSpot Webhooks with BoomTown when leads need to be mirrored from BoomTown into the wider HubSpot ecosystem.

FAQs

Specific to using BoomTown API API through Jentic.

Why is there no official OpenAPI spec for BoomTown API?

BoomTown does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BoomTown 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 BoomTown API use?

BoomTown uses OAuth 2.0 with authorization codes and refresh tokens, plus an x-api-key header containing the sha256 hash of your client_id and client_secret. The Access-Token header carries the user access token. Jentic stores both credentials in the vault and injects them at execution so they never enter the agent's context.

Can I assign a drip plan to a contact with the BoomTown API?

Yes. POST /contacts/{contactId}/assignedDripPlans with the target drip plan id, and use the /resume, /pause, and /terminate sub-paths to control it later. GET /contacts/{contactId}/assignableDripPlans lists which plans are valid for that contact's stage.

How do I subscribe to webhooks for new registrations through Jentic?

Search Jentic for 'subscribe to a BoomTown webhook', load the POST /webhooks/events/newRegistration schema, and execute it with your callback URL. Run pip install jentic, then call client.search, client.load, and client.execute in sequence.

What are the rate limits for the BoomTown API?

BoomTown does not document public rate limits in the OpenAPI spec; tenants on standard plans should batch contact lookups and rely on webhooks rather than polling. Use POST /contacts/textSearch with focused filters instead of broad GETs to avoid throttling.

How do I search transactions by status?

Use POST /organizations/{tenantId}/transactions/search for a filtered list and POST /organizations/{tenantId}/transactions/search/aggregate/status for counts grouped by status. Both accept the same filter body, so a dashboard can fetch totals and detail rows in two calls.

Can I log calls and texts to a contact's timeline?

Yes. POST /contacts/{contactId}/callLogs records call activity with duration and outcome, and GET /contacts/{contactId}/texts returns text history. POST /contacts/{contactId}/texts/markedAsRead clears unread counts after an agent responds in another tool.