Kindoo.Tech

Name: Kindoo.Tech API
Brand: Kindoo.Tech
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey129 EndpointsREST

For Agents

Provision sites, manage access rules and entry points, send invitations, and read entry-point logs across a Kindoo access-control deployment.

Install Jentic One Beta

Connect the Kindoo.Tech to your agent

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

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 | sh

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 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 Kindoo.Tech API.

Authenticate against Kindoo with ApiLogin and manage the resulting SessionTokenID

Create and edit sites (environments) with property metadata and contact details

Configure access rules and bind them to entry points

GET STARTED

Start building with Kindoo.Tech API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Kindoo.Tech, keeping it validated and agent-ready. Kindoo is an access-control and smart-property platform whose API exposes sites (called environments), entry points, access rules, users, agents, licenses, and the session lifecycle that authorizes every request. The 129-endpoint surface covers creating sites, configuring access rules, customising invitation emails per language, retrieving entry-point logs, and managing the SessionTokenID issued by ApiLogin. Use it to wire access control into property management or guest workflow systems.

Use Cases

Patterns agents use Kindoo.Tech API for, with concrete tasks.

★ Provision a new managed property

When a property manager onboards a new building, an integration can call POST /ApiLogin, then POST /KindooSaveEnvironmentNewWithoutType with the property details and the agent ID returned by KindooSearchAgents. The site is then ready for entry-point and rule configuration.

Authenticate with /ApiLogin, search for the right agent with /KindooSearchAgents, then POST /KindooSaveEnvironmentNewWithoutType with the property details.

Per-language invitation customisation

Operations teams can pull the available languages with POST /KindooGetAvailableLanguages and the keyword list with POST /KindooGetSiteInvitationEmailKeywords, then customise the invitation email for an existing or new Kindoo user. The same surface lets them remove a custom email and revert to Kindoo's default.

Call POST /KindooGetAvailableLanguages, then POST /KindooGetSiteInvitationVerifiedKindooUserEmailByLanguage for the chosen language and update the email body.

Entry-point log review

Security and operations teams can call POST /KindooGetSiteUserEntryPointLogs to retrieve the logs for an entry point, a specific user, or all access events on a site. Combined with POST /KindooGetEnvRuleWithEntryPoints the team can correlate access events with the rules that authorised them.

Call POST /KindooGetSiteUserEntryPointLogs with the site ID and date range and write the results to a daily security report.

Session hygiene

If an integration suspects a stale or compromised SessionTokenID, it can call POST /KindooGetAPISessions to inspect active sessions and POST /KillAllApiSessions or POST /KillMySession to invalidate them. This keeps the access-control plane locked down without rotating the underlying credentials.

List sessions via /KindooGetAPISessions and POST /KillAllApiSessions if more than one unexpected session is active.

Agent integration via Jentic

An access-control agent can use Jentic to discover the Kindoo login and site-creation operations, load their schemas, and execute them in sequence. The SessionTokenID is held in vault context, so the agent never sees the raw value once it has been issued.

Search Jentic for 'create a Kindoo site', load POST /ApiLogin and POST /KindooSaveEnvironmentNewWithoutType, and execute them in order.

Key Endpoints

129 endpoints — jentic publishes the only available openapi specification for kindoo.

METHOD

PATH

DESCRIPTION

POST

/ApiLogin

Authenticate and receive a SessionTokenID

POST

/KindooSaveEnvironmentNewWithoutType

Create a new site

POST

/KindooSaveEnvironment

Edit site details

POST

/KindooGetEnvironments

List or read environment objects

POST

/KindooGetSiteUserEntryPointLogs

Read entry-point logs

POST

/KindooGetEnvironmentRules

List access rules for a site

POST

/KillAllApiSessions

Invalidate all active sessions

POST

/KindooSearchAgents

Find an agent ID before creating a site

POST

/ApiLogin

Authenticate and receive a SessionTokenID

POST

/KindooSaveEnvironmentNewWithoutType

Create a new site

POST

/KindooSaveEnvironment

Edit site details

POST

/KindooGetEnvironments

List or read environment objects

POST

/KindooGetSiteUserEntryPointLogs

Read entry-point logs

Why Jentic?

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

Credential isolation

Kindoo login credentials live in the Jentic vault. Jentic performs the ApiLogin step and threads the resulting SessionTokenID through subsequent operations, so the agent process never reads the raw token.

Intent-based discovery

Agents search by intent, for example 'create a Kindoo site' or 'read Kindoo access logs', and Jentic returns the matching POST operation with its full input schema.

Time to first call

Direct integration: 2 to 4 days to handle the session model, error recovery, and 129-endpoint surface. Through Jentic: a few hours for the operations actually needed.

FAQs

Specific to using Kindoo.Tech API through Jentic.

Why is there no official OpenAPI spec for Kindoo.Tech?

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

Authentication is two-step: call POST /ApiLogin to obtain a SessionTokenID, then send that value in the SessionTokenID header on every subsequent request. Jentic stores the login credentials in the vault and manages the session token internally.

Can I create a new site with the Kindoo.Tech API?

Yes. After ApiLogin, call POST /KindooSearchAgents to get the right agent ID, then POST /KindooSaveEnvironmentNewWithoutType with the property name, contact details, and description. Edit the site later with POST /KindooSaveEnvironment.

What are the rate limits for the Kindoo.Tech API?

The OpenAPI specification does not declare explicit rate limits across the 129 endpoints. Reuse a single SessionTokenID across calls rather than logging in for every request, and call POST /KindooGetAPISessions if you need to inspect concurrent session counts.

How do I read entry-point logs with the Kindoo.Tech API through Jentic?

Run pip install jentic, search Jentic for 'read Kindoo entry point logs', load the POST /KindooGetSiteUserEntryPointLogs operation, and execute it with the site ID and date range. Jentic handles the ApiLogin step and supplies the SessionTokenID header.

Kindoo.Tech

Connect the Kindoo.Tech to your agent

Capabilities

Start building with Kindoo.Tech API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs