Knips App Knips API

Name: Knips API
Brand: Knips API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey, basic10 EndpointsREST

For Agents

Manage Knips product feeds, post their products and collections, attach contacts, and push or read posts and post requests.

Install Jentic One Beta

Connect the Knips API to your agent

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

List and create Knips feeds for organising product distribution

Read products and collections inside a specific Knips feed

Manage contacts attached to a Knips feed

Publish a post into a feed and read existing feed posts

GET STARTED

Start building with Knips API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Knips API, keeping it validated and agent-ready. Knips is a product feed and content distribution platform that helps brands push product, post, and contact data to retail and partner channels. The public API exposes feeds, the products and collections inside them, contacts attached to a feed, posts, and post requests, plus an authorization endpoint for issuing keys. It is well suited for retail teams syncing catalogues into Knips and for partner integrations that need to read or write feed-level content programmatically.

Use Cases

Patterns agents use Knips API for, with concrete tasks.

★ Catalogue Sync into Knips

Push a brand's product catalogue into Knips so it can be redistributed to retail partners. The /v1/feeds and /v1/feeds/{feedId}/products endpoints let an integrator create a feed and populate it with products, replacing CSV uploads with a real API. Best for brands with multiple sales channels who want one source of truth in their PIM and Knips as the distribution layer.

List products from the PIM, then for each call POST /v1/feeds/{feedId}/products on Knips feed 42 to upsert the product.

Partner Post Distribution

Distribute marketing posts to retail partners through Knips feeds. The /v1/feeds/{feedId}/posts endpoint publishes a post into a feed that subscribed partners can pull or be notified of, and /v1/feeds/{feedId}/post-requests captures partner asks for fresh content. Useful for brand teams who run frequent campaigns and need to keep partners equipped with current creatives.

POST a new post into Knips feed 42 with the provided creative URL and copy, and confirm it returns 201.

Contact Roster on Feeds

Manage the contacts attached to a Knips feed so the right people on the partner side receive updates. /v1/feeds/{feedId}/contacts lists and manages contacts at the feed level. Useful when an account changes hands at the partner and the brand team needs to update notification recipients without rebuilding the feed.

Add contact buyer@partner.com to Knips feed 42 and confirm it appears in the list response.

Agent-Driven Feed Operations via Jentic

Let an AI agent answer brand-team questions like 'how many products are in feed 42 today' or 'publish this campaign post to all active feeds' by calling Knips through Jentic. The agent searches Jentic for the matching operation, loads the schema, and executes with the API key drawn from the Jentic vault. Faster than wiring a Knips client into an internal tool.

Through Jentic, search for 'list Knips feeds', load /v1/feeds, and report the count of feeds returned.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/feeds

List feeds

GET

/v1/feeds/{feedId}/products

List products in a feed

GET

/v1/feeds/{feedId}/collections

List collections in a feed

GET

/v1/feeds/{feedId}/contacts

List contacts on a feed

GET

/v1/feeds/{feedId}/posts

List posts in a feed

POST

/v1/feeds/{feedId}/post-requests

Create a post request

POST

/v1/authorization

Authorise an integration

GET

/v1/feeds

List feeds

GET

/v1/feeds/{feedId}/products

List products in a feed

GET

/v1/feeds/{feedId}/collections

List collections in a feed

GET

/v1/feeds/{feedId}/contacts

List contacts on a feed

GET

/v1/feeds/{feedId}/posts

List posts in a feed

Why Jentic?

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

Credential isolation

Knips API keys and Basic auth credentials are stored encrypted in the Jentic vault. Agents call /v1/feeds, /v1/feeds/{feedId}/products, and /v1/feeds/{feedId}/posts through scoped Jentic tools without holding the raw x-api-key.

Intent-based discovery

Agents search by intent (e.g., 'list Knips feeds', 'publish a Knips post') and Jentic returns the matching operation with its schema so the agent picks the right endpoint without reading the docs.

Time to first call

Direct Knips integration: 1 day for auth wiring, feed identifier lookup, and post format handling. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Knips API through Jentic.

Why is there no official OpenAPI spec for Knips API?

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

The Knips API supports HTTP Basic auth and an API key sent in the x-api-key header. Through Jentic, both forms of credential are stored in the Jentic vault and injected at execution time so the agent never holds the raw values.

Can I push products into a Knips feed via the API?

Yes. /v1/feeds/{feedId}/products exposes the products inside a feed and supports the writes needed to add or update products. Use it instead of CSV uploads when integrating from a PIM or e-commerce backend.

What are the rate limits for the Knips API?

Knips does not publish a public rate limit and the spec does not declare one. Treat per-feed write endpoints as moderately throttled and avoid tight loops; cache feed and product reads where possible.

How do I publish a post to a Knips feed from an AI agent through Jentic?

Search Jentic for 'publish a Knips post', load /v1/feeds/{feedId}/posts, and execute with the feed id and post payload. Jentic injects the x-api-key header from the vault so the agent only deals with the post content.

Does the Knips API support partner-driven post requests?

Yes. POST /v1/feeds/{feedId}/post-requests captures a partner's request for new content against a specific feed, which the brand team can then fulfil with /v1/feeds/{feedId}/posts.