Kimp360 API

Name: Kimp360 API
Brand: Kimp360 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey7 EndpointsREST

For Agents

Submit and read design tasks against a Kimp360 workspace, and list the brand, label, tag, and request-type metadata that tasks reference.

Install Jentic One Beta

Connect the Kimp360 API to your agent

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

Create a new design task to enter the Kimp360 production queue

Read a design task by ID to check its current state

List the brands available on a Kimp360 workspace

List labels and tags used to categorise design requests

GET STARTED

Start building with Kimp360 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Kimp360 API for, with concrete tasks.

★ Submit design requests from a marketing tool

When a marketing team finalises a brief in their planning tool, an integration can call POST /card to create the corresponding design task in Kimp360 with the brand, request type, and tags already populated. The team avoids retyping the brief into the Kimp360 portal and the task enters the queue with consistent metadata.

POST a card to /card with brandId, requestTypeId, and the brief text, then store the returned task ID against the source ticket.

Status check for in-flight design tasks

A status dashboard can call GET /card/{id} for each open task to read its current production state and surface that back in the source planning tool. Combined with GET /brands the dashboard can group tasks by brand for at-a-glance reporting.

For each open task ID, call GET /card/{id} and write the state back to the source row.

Metadata sync into a brief template

Before a user fills in a brief in another tool, an automation can call GET /brands, GET /labels, GET /tags, and GET /card-types to populate the dropdowns. The brief then submits cleanly via POST /card with valid IDs.

Call GET /brands and GET /card-types and pass the returned IDs into the brief form's dropdown options.

Agent integration via Jentic

An agent can use Jentic to discover the Kimp360 task creation operation, load its schema, and execute POST /card with the brief details supplied by the user. The x-api-key is held in the vault, so the agent never reads the raw value.

Search Jentic for 'create a Kimp360 design task', load POST /card, and execute it with the supplied brief, brandId, and requestTypeId.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/card

Create a new design task

GET

/card/{id}

Read a design task by ID

GET

/brands

List brands on the workspace

GET

/brands/{id}

Read a single brand

GET

/labels

List labels

GET

/tags

List tags

GET

/card-types

List request types

POST

/card

Create a new design task

GET

/card/{id}

Read a design task by ID

GET

/brands

List brands on the workspace

GET

/brands/{id}

Read a single brand

GET

/labels

List labels

GET

/tags

List tags

Why Jentic?

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

Credential isolation

The Kimp360 x-api-key is stored encrypted in the Jentic vault. Agents receive a scoped execution context and never read the raw key.

Intent-based discovery

Agents search by intent, for example 'create a Kimp360 design task', and Jentic returns the POST /card operation with its full request schema.

Time to first call

Direct integration: a few hours to wire up the seven endpoints. Through Jentic: a few minutes to search, load, and execute.

FAQs

Specific to using Kimp360 API through Jentic.

Why is there no official OpenAPI spec for Kimp360 API?

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

Kimp360 authenticates with an x-api-key header. Jentic keeps that key in the vault and injects it per request, so the agent process never reads the raw value.

Can I create a design task with the Kimp360 API?

Yes. POST to /card with a brandId, requestTypeId, and the brief content. The new task enters the Kimp360 production queue and the response includes the task ID you can use later with GET /card/{id}.

What are the rate limits for the Kimp360 API?

The OpenAPI specification does not declare explicit rate limits for the seven endpoints. Cache the brand, label, tag, and request-type lists rather than re-fetching them on every brief, and back off if the API returns a 429.

How do I submit a design request with the Kimp360 API through Jentic?

Run pip install jentic, search Jentic for 'create a Kimp360 design task', load the POST /card operation, and execute it with the brief, brandId, and requestTypeId. Jentic supplies the x-api-key header from the vault.