TenAnts API

Name: TenAnts API API
Brand: TenAnts API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey3 EndpointsREST

For Agents

List and create tenants and list properties through the TenAnts property management API.

Connect the TenAnts API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 TenAnts API API.

List every tenant on the account through GET /tenants

Add a new tenant record with POST /tenants for onboarding workflows

List the property records associated with the account via GET /properties

Reconcile tenant rosters between TenAnts and an external billing system using ids returned by GET /tenants

GET STARTED

Start building with TenAnts API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for TenAnts API, keeping it validated and agent-ready. TenAnts is a Utilihub-hosted property and tenant management API that exposes a small but focused surface for syncing tenant rosters and property records into downstream systems. The three endpoints cover listing tenants, creating tenants, and listing properties, suitable as a lightweight integration source for utility billing, maintenance scheduling, or compliance reporting workflows. It is intended for property managers and small landlord platforms that need basic tenant and property identifiers programmatically.

Use Cases

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

★ Tenant Roster Sync to Billing

Property managers running utility submetering or split-billing want the tenant list mirrored into their billing system. GET /tenants returns the canonical roster, and a scheduled job can diff that against the billing platform and create or close accounts accordingly.

Call GET /tenants on an hourly schedule and reconcile against the billing system, calling its create-account endpoint for any new TenAnts ids.

Lease Onboarding Automation

When a new lease is signed, an onboarding workflow can call POST /tenants to register the resident in TenAnts so subsequent maintenance, communications, and billing flows have a canonical record. This avoids manual entry in the property manager's dashboard.

POST /tenants with the new resident's name, contact details, and property id immediately after the lease document is e-signed.

Property Portfolio Snapshot

Investors or asset managers running periodic portfolio reviews can call GET /properties to pull the property list and combine it with GET /tenants to produce occupancy snapshots without exporting CSVs from the TenAnts UI.

GET /properties followed by GET /tenants, then group tenants by property id to compute occupancy per asset.

Agent-Driven Property Operations via Jentic

Property-ops agents can keep the tenant roster up to date and answer questions about properties through Jentic without provisioning the TenAnts API key in the agent environment. Jentic exposes the three operations by intent and isolates the key.

Use Jentic to search 'add a new tenant', load the POST /tenants schema, and execute with the new resident's details.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/tenants

List tenants on the account

POST

/tenants

Create a new tenant

GET

/properties

List property records

GET

/tenants

List tenants on the account

POST

/tenants

Create a new tenant

GET

/properties

List property records

Why though Jentic?

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

Credential isolation

TenAnts API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw key never enters the agent's prompt or context window.

Intent-based discovery

Agents search by intent (e.g., 'list tenants' or 'add a new tenant') and Jentic returns the matching TenAnts operation with its input schema.

Time to first call

Direct TenAnts integration: a few hours for auth and parameter wiring. Through Jentic: minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AppFolio API

AppFolio is a full property management platform with a richer API surface than TenAnts.

Choose AppFolio when the workflow needs maintenance, accounting, and communications endpoints beyond tenant and property listing.

Alternative

Buildium API

Buildium is another property management platform offering broader CRUD on tenants, leases, and accounting.

Choose Buildium when the workflow needs full lease and accounting operations rather than the lightweight TenAnts surface.

Complementary

Stripe API

Stripe handles rent collection that often follows tenant onboarding in TenAnts.

Use Stripe alongside TenAnts to charge rent or set up recurring rent billing once a tenant is registered.

FAQs

Specific to using TenAnts API API through Jentic.

Why is there no official OpenAPI spec for TenAnts API?

Utilihub publishes documentation but not a maintained OpenAPI document for TenAnts. Jentic generates and maintains this spec so that AI agents and developers can call TenAnts 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 TenAnts API use?

TenAnts uses an API key passed via header (apiKey scheme). Through Jentic the key is stored encrypted in the vault and only injected at execution time, so the raw secret never reaches the agent.

Can I create a new tenant with the TenAnts API?

Yes. POST /tenants accepts the tenant's contact details and property linkage and returns the new tenant id, suitable for triggering at lease-signing time.

What are the rate limits for the TenAnts API?

The OpenAPI spec does not declare numeric rate limits. The three endpoints are low-volume by nature — confirm with Utilihub support before running batch syncs above a few hundred requests per minute.

How do I list every tenant under management through Jentic?

Search Jentic for 'list all tenants', load the GET /tenants schema, and execute. The response returns the full roster with ids that can be used to reconcile against external systems.

Does the TenAnts API expose property creation?

The current spec exposes GET /properties for listing only. Property creation is not in the public API surface — manage properties through the Utilihub UI or contact Utilihub support for portfolio onboarding.