Install Jentic One Beta

Connect the Door Knock Pro Public API to your agent

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

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdoorknockpro.com%2Fdoor-knock-pro" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdoorknockpro.com%2Fdoor-knock-pro" | 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 Door Knock Pro Public API.

Create, update, and soft-delete leads and read a lead's knock and activity history

Schedule and manage appointments for field sales reps

List territories and search the leads within a given territory

Look up company users, teams, lead statuses, and property types

Subscribe to outbound webhooks for lead and appointment events

GET STARTED

Start building with Door Knock Pro Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Door Knock Pro Public API for, with concrete tasks.

★ Agent-driven lead capture

An AI agent connected through Jentic can turn field notes into Door Knock Pro records: create a lead from a knock, set its status, and book a follow-up appointment for the assigned rep. Each operation returns the created record so the agent can confirm the lead and appointment exist and report the appointment time back to the rep.

Create a lead for a newly knocked address, set its lead status, and schedule a follow-up appointment for the assigned rep.

Territory-based lead routing

Door Knock Pro organizes leads by territory, so an agent can pull the leads within a specific territory and distribute follow-ups across the reps assigned there. Combined with the users and teams lookups, this lets a routing agent keep each rep's workload tied to their territory without exporting data to a spreadsheet.

Search the leads within a territory, list the users assigned to it, and report how many open leads each rep is responsible for.

Real-time CRM sync via webhooks

Door Knock Pro emits outbound webhooks for lead and appointment events, so an external system can stay in sync without polling. An agent can register a webhook endpoint, confirm it with a synthetic ping delivery, and later replay any failed delivery so no lead update is lost during an outage.

Create a webhook endpoint for lead events, trigger a test ping to confirm it, and replay the most recent failed delivery.

Key Endpoints

31 endpoints — the door knock pro api lets external systems read and write the records behind a door-to-door sales operation: leads, appointments, territories, users, and knock and activity history.

METHOD

PATH

DESCRIPTION

GET

/v1/leads

List leads

POST

/v1/leads

Create a lead

PATCH

/v1/leads/{id}

Update a lead

GET

/v1/leads/{id}/history

Activity history for a single lead

GET

/v1/appointments

List appointments

POST

/v1/appointments

Create an appointment

GET

/v1/territories/{id}/leads

Search leads within a territory

POST

/v1/webhooks

Create a webhook endpoint

GET

/v1/leads

List leads

POST

/v1/leads

Create a lead

PATCH

/v1/leads/{id}

Update a lead

GET

/v1/leads/{id}/history

Activity history for a single lead

GET

/v1/appointments

List appointments

POST

/v1/appointments

Create an appointment

GET

/v1/territories/{id}/leads

Search leads within a territory

POST

/v1/webhooks

Create a webhook endpoint

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Door Knock Pro by hand means managing its two-layer auth, a company X-Api-Key header on every request plus an optional per-user bearer token from the login endpoint, and coding around its per-key request limits. Through Jentic you install once, import Door Knock Pro from the API Directory, store the key once, and your agent calls it.

Permission scoping

Door Knock Pro puts resource ids in the URL path, for example a lead or webhook id, and its company API key makes cross-company access impossible by design. You choose the operations your agent may call, so destructive ones such as deleting a lead or rotating a webhook secret are not included unless you add them.

Credential isolation

Your Door Knock Pro API key, and any per-user access token, are stored encrypted by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a lead' or 'search leads in a territory', and Jentic returns the matching Door Knock Pro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Door Knock Pro Public API through Jentic.

What authentication does the Door Knock Pro API use?

The Door Knock Pro API uses a two-layer model per its OpenAPI spec: a company-level API key sent in the X-Api-Key header on every request, plus an optional per-user access token sent as a bearer token in the Authorization header and obtained from the login endpoint. The API key alone is enough for server-to-server use, while the user token attributes actions to a specific rep. Through Jentic both credentials are stored encrypted by your own Jentic One instance and injected at call time.

Is there a Door Knock Pro MCP server?

You don't need an MCP server to give your agent the Door Knock Pro API. Jentic connects it directly from the API Directory: import Door Knock Pro, store your key once, and your agent calls its operations. Operations are discovered on demand, so no extra server's tool definitions are loaded into the agent's context.

Can I limit what my agent is allowed to do with the Door Knock Pro API?

Yes. Write a rule that allows only the lead and appointment read and create operations, so your agent can log knocks and book visits but cannot delete leads or rotate webhook signing secrets, and every call it makes is logged. The company API key already confines all access to your own company's data, so the agent can never reach another tenant.

Can I search leads within a territory using the Door Knock Pro API?

Yes. The territories endpoints list your configured territories and return the leads inside a specific territory, which an agent can combine with the users and teams lookups to route follow-ups to the reps assigned there. Lead and property-type lookups let the agent filter those results by status or property type.

What are the rate limits for the Door Knock Pro API?

Door Knock Pro's spec documents 60 requests per minute per company API key and 100 requests per minute per user access token, so one user cannot exhaust the company quota. Exceeding a limit returns an HTTP 429 response; check the developer documentation for the current figures before relying on them in production.

How do I create a lead with the Door Knock Pro API through Jentic?

Install Jentic One, import Door Knock Pro from the API Directory, and store your company API key once. Your agent then searches by intent, for example 'create a lead', and Jentic returns the matching operation with its input schema so the agent sends the right fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Door Knock Pro Public API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey, bearer31 EndpointsREST

For Agents

Read and write leads, appointments, territories, and users for a door-to-door sales team, track knock and activity history, and manage outbound webhooks. A company API key scopes every request to one company, with an optional per-user token for attributed actions.

Use for: List all leads in a territory, Create a new lead from a door knock, Schedule an appointment for a sales rep, Get the activity history for a lead

Not supported: Does not handle payment collection, commission payouts, or route optimization. Use for managing door-to-door sales leads, appointments, and territories only.

The Door Knock Pro API lets external systems read and write the records behind a door-to-door sales operation: leads, appointments, territories, users, and knock and activity history. It exposes lead statuses and property-type lookups, searches the leads inside a territory, and manages outbound webhook subscriptions with delivery inspection and replay. A company-level API key scopes every request to the company that owns it, and an optional per-user access token attributes actions to a specific rep.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

75%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

12%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

94%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Door Knock Pro Public API to your agent

Capabilities

Start building with Door Knock Pro Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Door Knock Pro Public API

Jentic AI Readiness Score

Door Knock Pro Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness