canonical: https://jentic.com/apis/kindoo.tech/kindoo # Kindoo.Tech 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. ## For AI agents Provision sites, manage access rules and entry points, send invitations, and read entry-point logs across a Kindoo access-control deployment. ## Scope Does not handle billing, video surveillance, or building HVAC - use for Kindoo site provisioning, access rules, entry points, and session management only. ## Capabilities - 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 - Customise invitation emails per language for both new and existing Kindoo users - Retrieve entry-point logs for a site, user, or rule - List and manage active API sessions, including killing one or all sessions - Search agents and assign them to a site during creation ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a Kindoo site', load POST /ApiLogin and POST /KindooSaveEnvironmentNewWithoutType, and execute them in order. ## Key endpoints | 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 | ## Key resources - **Authentication and Session Management** — Authenticate, list sessions, and kill active sessions - **Environment Management** — Create and edit sites and read environment data - **Access Rule Management** — Configure access rules and bind them to entry points - **Entry Point Management** — Manage entry points and read their access logs - **User Management** — Read site users and manage their invitations - **Licenses Provisioning** — Provision and manage licenses across sites ## Why Jentic - **Setup:** Wiring Kindoo.Tech by hand means logging in for a SessionTokenID, replaying it on every SOAP-style POST to the webservice.asmx host, and managing session teardown yourself. Through Jentic you install once, import Kindoo.Tech from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Kindoo.Tech drives everything through POST operations that carry the site and environment targets in the request body rather than as a URL path resource, so scope by operation: limit the agent to the operations it needs, such as reading environments or entry-point logs, and leave session-killing or rule changes out unless you add them. - **Credential handling:** Your Kindoo.Tech credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Kindoo site environments' or 'read entry-point access logs', and Jentic returns the matching Kindoo.Tech operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Genetec API** — Genetec is a unified physical-security platform covering access control and video - **1Password Events API** — 1Password Events streams credential access events alongside Kindoo physical access events - **Salesforce API** — Salesforce holds the customer record that owns a Kindoo-managed property ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Kindoo.Tech API? Yes. Because Jentic One is self-hosted, you decide which of the 129 Kindoo operations your agent may call, and your own rules are enforced at execution time. Kindoo carries its site and environment targets in the request body rather than in the URL, so you scope by operation: grant read-only calls like POST /KindooGetEnvironments or POST /KindooGetSiteUserEntryPointLogs while withholding write and destructive ones such as POST /KindooSaveEnvironment, rule changes, or POST /KillAllApiSessions. The credential is held by your own instance and injected only for the operations you have allowed, so the agent can never reach beyond that set.