Integration
Connect Livabl to DistrictAPI
When New Leads fires in Livabl, your agent runs Batch lookup districts in DistrictAPI. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Livabl and DistrictAPI to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Livabl can start in DistrictAPI
When New Leads in Livabl
then Batch lookup districts in DistrictAPI
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Livabl and DistrictAPI
Triggers and actions 4 triggers · 13 actions
- New Leads
Triggers when a new lead arrives for any of the company's communities.
- New Livabl Pro Leads
Triggers when a new Livabl Pro agent lead arrives.
- Updated Community
Triggers when a community is added or its details change.
- Updated Company
Triggers when the company's details (name or number of developments) change.
- Get Appointment Lead
Returns the appointment-request lead for an appointment ID, including the requested date and time.
- Get Company Details
Returns the company the API key belongs to: its name, ID and number of developments.
- Get Lead
Returns one lead by its lead ID, with the contact's name, email, phone, message and the development they asked about.
- List Communities
Returns the communities (developments) the API key can access.
- List Development Leads
Returns the leads for one development, optionally limited to a date range.
- Batch lookup districts
Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one.
- Find districts by name, state or county
Returns the school districts matching the name, state or county you supply.
- Get district
Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary.
- Get school
Returns the full profile of one school, including its address, grades served, enrollment and parent district.
- Get school's district
Returns the full profile of the school district a given school belongs to.
- List districts
Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID.
- List schools
Returns the schools near a street address or a pair of coordinates, within the radius you choose.
- List schools by district
Returns the open schools inside a given school district, optionally limited to one school type or to charter schools.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Livabl
Livabl to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Livabl to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Livabl to MailchimpMailchimp marketing automation and email platform.
Livabl to StripeStripe is a payment processing platform for online businesses.
Livabl to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Livabl to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into DistrictAPI
Arxiv to DistrictAPIOpen-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...
HubSpot to DistrictAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to DistrictAPIGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to DistrictAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Livabl and DistrictAPI, answered
What can start an automation from Livabl?
Any of Livabl's 4 triggers in the catalog, including New Leads, New Livabl Pro Leads, Updated Community and Updated Company. Describe the moment in plain language and your agent picks the right one.
What can your agent do in DistrictAPI when something happens in Livabl?
Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DistrictAPI to Livabl?
DistrictAPI has no triggers in the catalog today, so automations start in Livabl. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it.
Do I have to build a connector for Livabl or DistrictAPI?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Livabl and DistrictAPI without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.