Getknit Knit Unified Integration API

Name: Knit Unified Integration API
Brand: Knit Unified Integration API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer6 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Knit Unified Integration API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Knit Unified Integration 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%2Fgetknit.dev%2Fgetknit" | 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%2Fgetknit.dev%2Fgetknit" | 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 Knit Unified Integration API.

Trigger a one-off data synchronization from a downstream provider via POST /syncs/start

Submit a candidate application to an ATS through a single normalized POST /ats/applications

List CRM contacts across the user's connected CRM provider through GET /crm/contacts

GET STARTED

Start building with Knit Unified Integration API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Knit Unified Integration API for, with concrete tasks.

★ Vendor-Agnostic ATS Submission

Build a careers page that submits applications into whichever ATS the customer has connected through Knit. The integration calls POST /ats/applications with a normalized payload and Knit translates it for Greenhouse, Lever, Workable, or other connected ATS providers. Setup typically takes hours rather than the per-ATS implementation it would otherwise require.

Call POST /ats/applications with firstName, lastName, email, and jobId for the Knit-connected user and confirm a 200 response.

Unified CRM Contact Pull

Pull CRM contacts into a downstream tool without writing per-CRM code. The integration calls GET /crm/contacts and Knit normalizes the response across HubSpot, Salesforce, Pipedrive, and others. Useful for AI products that enrich CRM data and need broad coverage from day one.

Call GET /crm/contacts with the user's Knit Bearer token and paginate until all contacts have been retrieved.

Cross-Ticketing Helpdesk Audit

Build a customer support audit dashboard that lists tickets from every helpdesk a customer might use. The integration calls GET /ticketing/tickets.list and Knit normalizes Zendesk, Freshdesk, Intercom, and others into a common ticket schema. Avoids the multi-month effort of per-vendor connectors.

Call GET /ticketing/tickets.list and aggregate tickets opened in the last 7 days for a single Knit-connected customer.

AI Agent Multi-Provider Connector

An AI agent that needs to read or write across HR, CRM, accounting, and meetings calls Knit through Jentic instead of integrating each underlying SaaS. The agent searches for the right normalized operation, executes it, and lets Knit handle the per-vendor differences. Time-to-coverage drops from months to under a day.

Search Jentic for 'list CRM contacts via Knit', load the schema for GET /crm/contacts, and execute with a Bearer token issued by Knit.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for the knit unified integration api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/syncs/start

Start a data synchronization for a connected end-user account

POST

/ats/applications

Submit a candidate application through a normalized ATS schema

GET

/crm/contacts

List CRM contacts across the connected provider

POST

/accounting/journal-entries

Create a journal entry in the connected accounting system

GET

/ticketing/tickets.list

List support tickets across the connected ticketing tool

GET

/meeting/transcript

Retrieve a meeting transcript from the connected meetings provider

POST

/syncs/start

Start a data synchronization for a connected end-user account

POST

/ats/applications

Submit a candidate application through a normalized ATS schema

GET

/crm/contacts

List CRM contacts across the connected provider

POST

/accounting/journal-entries

Create a journal entry in the connected accounting system

GET

/ticketing/tickets.list

List support tickets across the connected ticketing tool

Why Jentic?

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

Setup

Wiring Knit by hand means setting its bearer auth, managing per-end-user tokens, and normalizing HR, ATS, CRM, accounting, ticketing, and meeting calls across providers yourself. Through Jentic you install once, import the Knit Unified Integration API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Knit's unified calls target categories through the request body and route rather than a resource id in the path, so you limit the agent to the operations it needs, such as listing CRM contacts or reading a meeting transcript. Because you pick the operation set, writes like posting a journal entry are not reachable unless you add them.

Credential isolation

Your Knit token 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.

Intent-based discovery

Agents search Jentic by intent such as 'list CRM contacts' or 'submit a candidate application', and Jentic returns the matching normalized Knit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Knit Unified Integration API through Jentic.

Why is there no official OpenAPI spec for the Knit Unified Integration API?

Knit publishes documentation but does not host a maintained OpenAPI specification covering the unified endpoints. Jentic generates and maintains this spec so that AI agents and developers can call Knit 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 Knit API use?

Knit uses HTTP Bearer authentication with a token issued per connected end-user account. The token both identifies the calling app and selects which downstream provider Knit should route the request to. Jentic stores the Bearer token in its encrypted vault.

Can I list CRM contacts across different CRMs with the Knit API?

Yes. Call GET /crm/contacts with the Bearer token issued for the connected end-user account; Knit translates the request to whichever CRM that user has linked, normalizes the response, and returns a unified contact schema.

What are the rate limits for the Knit API?

Knit applies per-app and per-end-user throttles that are not encoded in the spec. Plan for sustained throughput around 10 requests per second per end-user token and back off when 429 responses arrive with a Retry-After header.

How do I create an accounting journal entry through Jentic?

Search Jentic for 'create a Knit journal entry', load the schema for POST /accounting/journal-entries, and execute with the normalized journal entry payload. Jentic injects the Bearer token automatically so credentials never enter the agent context.

Does the Knit API support pulling meeting transcripts?

Yes. Call GET /meeting/transcript with the Bearer token for an end-user who has connected a meetings provider; Knit returns the transcript using a unified schema regardless of whether the underlying tool is Zoom, Google Meet, or another provider.

Can I limit what my agent is allowed to do with the Knit Unified Integration API?

Yes. Because Jentic One is self-hosted, you decide which of Knit's normalized operations your agent can reach, and its calls target categories through the route and request body rather than a resource id, so you can allow read operations like GET /crm/contacts or GET /meeting/transcript while excluding everything else. Writes such as POST /accounting/journal-entries or POST /ats/applications are not reachable unless you add them to the operation set you grant. Your rules also govern the Bearer token your instance holds, so the agent can only invoke the operations and credentials you have permitted.

Getknit Knit Unified Integration API

Connect the Knit Unified Integration API to your agent

Capabilities

Start building with Knit Unified Integration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs