canonical: https://jentic.com/apis/kimp360.com/kimp360 # Kimp360 API Jentic publishes the only available OpenAPI specification for Kimp360 API, keeping it validated and agent-ready. Kimp360 is a design-as-a-service workflow tool, and its API exposes the records that drive a design request: brands, labels, tags, request types, and the design tasks themselves. The current surface lets a client list brands and supporting metadata, fetch a specific design task, and submit a new task into the queue. Authentication is by x-api-key header. ## For AI agents Submit and read design tasks against a Kimp360 workspace, and list the brand, label, tag, and request-type metadata that tasks reference. ## Scope Does not host design files, render previews, or process payments - use for submitting and reading Kimp360 design tasks and their reference metadata only. ## Capabilities - 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 - List the request types that a task can be filed under - Fetch a single brand record for use in a task submission ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a Kimp360 design task', load POST /card, and execute it with the supplied brief, brandId, and requestTypeId. ## Key endpoints | 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 | ## Key resources - **Tasks** — Create and read individual design tasks (cards) - **Brands** — List and read brand records that tasks belong to - **Labels** — List labels that classify design tasks - **Tags** — List tags applied to design tasks - **Request Types** — List the request types a task can be filed under ## Why Jentic - **Setup:** Wiring Kimp360 by hand means learning its x-api-key header auth and handling the api.kimp.kim host and its errors yourself. Through Jentic you install once, import Kimp360 from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Kimp360 identifies a design task in the URL path only on reads (`/card/{id}`), while submissions post the task in the request body, so scope by operation: limit the agent to the operations it needs, such as submitting a design card or reading brands and labels, and leave the rest out unless you add them. - **Credential handling:** Your Kimp360 API key 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 'submit a design task' or 'read a design card', and Jentic returns the matching Kimp360 operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Asana API** — Asana tracks the upstream marketing project that produces a Kimp360 design brief - **Monday.com API** — Monday.com runs the marketing board that hands briefs over to Kimp360 - **Trello API** — Trello can be used as a free-form design queue without Kimp360's design service - **Airtable API** — Airtable can hold the canonical brief library that feeds Kimp360 task submissions ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Kimp360 API? Yes. Because you run Jentic One yourself, your own rules decide which Kimp360 operations and credentials the agent may use, and Kimp360 scopes cleanly by operation. You can allow only what a job needs, such as submitting a design card with POST /card or reading reference data through GET /brands, GET /labels, GET /tags, and GET /card-types, while leaving the rest out. If an agent only files briefs, you can grant POST /card and GET `/card/{id}` and withhold everything else.