What authentication does the Livabl API use?

Livabl uses API key authentication. Builder Dashboard accounts can generate up to 20 API keys, scoped per company or per community, in Settings > Integrations. Through Jentic, the key is held in your Jentic One instance and injected at execution time so agents never receive the raw value.

Can I pull leads for a specific development with the Livabl API?

Yes. GET /Company/Communities/{DevelopmentID}/Leads returns leads scoped to a single development id, which matches how Builders typically assign onsite sales staff. For company-wide pulls use GET /Company/Communities/Leads instead.

What are the rate limits for the Livabl API?

Rate limits are not formally published in the spec; access is gated by Featured/Verified Builder eligibility and per-key issuance. Build agents to poll on a per-minute or per-five-minute cadence rather than continuously, and prefer per-development calls when you only need a subset of leads.

How do I sync Livabl leads through Jentic?

Run pip install jentic, then search for 'pull new Livabl leads'. Jentic returns GET /Company/Communities/Leads. Load the schema, execute, and diff the result against your CRM to detect new leads. For lead detail call GET /Company/Communities/Leads/{LeadID}.

Can I limit what my agent is allowed to do with the Livabl API?

Yes. Because you run Jentic One yourself, your own rules decide which Livabl operations and credentials the agent may use. Every Livabl endpoint here is a GET, so you can allow the agent to read leads and community data while it performs no writes, and because the development and lead ids sit in the URL path (/Company/Communities/{DevelopmentID}/Leads, /Company/Communities/Leads/{LeadID}), a rule can pin the agent to a single development or to lead detail lookups only. You can also restrict which stored per-community API key is injected at execution time so the agent only ever reaches the communities you permit.