KiSSFLOW REST API

Name: KiSSFLOW REST API
Brand: KiSSFLOW REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey13 EndpointsREST

For Agents

Submit, approve, reject, and inspect Kissflow process requests across any process configured in a Kissflow account.

Install Jentic One Beta

Connect the KiSSFLOW REST API to your agent

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

Create and immediately submit a request inside a named Kissflow process

Approve, reject, or complete an input step on an in-flight request

Seek clarification on a submitted request before approving

GET STARTED

Start building with KiSSFLOW REST API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for KiSSFLOW REST API, keeping it validated and agent-ready. Kissflow is a process and workflow platform, and its REST API exposes the operations that drive a request through a process: create a draft, submit it, approve, reject, complete an input step, seek clarification, and read progress. The 13-endpoint surface is shaped around a single process_name path parameter so the same calls reach any process in the account, with authentication by an api_key header and an optional email_id header for acting on behalf of another user.

Use Cases

Patterns agents use KiSSFLOW REST API for, with concrete tasks.

★ Drive process requests from a chat surface

Operations teams can let employees submit standard requests like leave or travel through chat or a custom form, with the bot calling POST /{process_name}/submit to create and submit the request in a single call. The same surface lets approvers approve or reject from chat via POST /{process_name}/{request_id}/approve.

POST a payload to /{process_name}/submit with the form fields and surface the returned request_id back to the user.

Approval routing through an existing tool

When approvers prefer their existing inbox or task tool, an integration can read pending requests with GET /{process_name}/list/p{page}/{size} and post the action with POST /{process_name}/{request_id}/approve or .../reject. This keeps Kissflow as the system of record while the approval UX lives elsewhere.

List pending requests, route each one to the approver's tool, and POST the approve or reject endpoint with their decision.

Process progress dashboard

A status dashboard can poll GET /{process_name}/{request_id}/progress for in-flight requests and combine it with GET /{process_name}/{request_id}/read to show field values and the current step. The combination is enough to render a complete request card without screen-scraping Kissflow.

Call GET /{process_name}/{request_id}/progress for each open request and write the current step to the dashboard.

Agent integration via Jentic

An operations agent can use Jentic to discover the Kissflow approve and submit operations, load their schemas, and execute them with a vaulted api_key. The agent never sees the raw key and can act on behalf of another user by passing the email_id header through Jentic.

Search Jentic for 'submit a Kissflow process request', load POST /{process_name}/submit, and execute it with the process name and form payload.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/process

List processes on the account

POST

/{process_name}/submit

Create and submit a request

POST

/{process_name}/{request_id}/approve

Approve a request

POST

/{process_name}/{request_id}/reject

Reject a request

POST

/{process_name}/{request_id}/done

Complete an input step

GET

/{process_name}/{request_id}/read

Read request details

GET

/{process_name}/{request_id}/progress

Read workflow progress

GET

/{process_name}/list/p{page}/{size}

List paginated requests

GET

/process

List processes on the account

POST

/{process_name}/submit

Create and submit a request

POST

/{process_name}/{request_id}/approve

Approve a request

POST

/{process_name}/{request_id}/reject

Reject a request

POST

/{process_name}/{request_id}/done

Complete an input step

Why Jentic?

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

Credential isolation

The Kissflow api_key lives encrypted in the Jentic vault. Jentic injects it on each call and lets the caller specify an email_id at execution time so the agent can act on behalf of a user without holding raw credentials.

Intent-based discovery

Agents search by intent, for example 'submit a Kissflow process request' or 'approve a Kissflow request', and Jentic returns the matching POST operation under the right process_name template.

Time to first call

Direct integration: about a day to handle the path templating, on-behalf-of header, and approval semantics. Through Jentic: under an hour for the operations actually needed.

FAQs

Specific to using KiSSFLOW REST API through Jentic.

Why is there no official OpenAPI spec for KiSSFLOW REST API?

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

Kissflow authenticates with an api_key header. An optional email_id header lets the caller act on behalf of another user. Jentic stores the api_key in the vault and supports passing through a chosen email_id at execution time.

Can I approve a request with the KiSSFLOW REST API?

Yes. POST to /{process_name}/{request_id}/approve. Reject with the parallel /reject endpoint and complete an input step with /done. Each call uses the same path shape and authenticates with the api_key header.

What are the rate limits for the KiSSFLOW REST API?

The OpenAPI specification does not declare explicit rate limits across the 13 endpoints. Use GET /{process_name}/list/p{page}/{size} with a sensible page size for reporting rather than re-pulling the full list, and back off if a 429 is returned.

How do I submit a Kissflow request with the KiSSFLOW REST API through Jentic?

Run pip install jentic, search Jentic for 'submit a Kissflow process request', load the POST /{process_name}/submit operation, and execute it with the process name and form payload. Jentic supplies the api_key header from the vault.

KiSSFLOW REST API

Connect the KiSSFLOW REST API to your agent

Capabilities

Start building with KiSSFLOW REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs