Ziflow API

Name: Ziflow API
Brand: Ziflow API
Availability: InStock

✓ Official Vendor SpecAI/MLLanguage ModelsapiKey, basic, bearer95 EndpointsREST

For Agents

Programmatically create new proof, get proofs. Covers 95 operations with apiKey, basic, bearer authentication.

Use for: I need to new proof, I want to proofs, Search for proofs, Find all proofs activity

Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.

Welcome to the Ziflow API The Ziflow API is built to allow you to easily and quickly embed Ziflow’s proofing features in your own application or create an integration between Ziflow and any other application. This API is the same one we use to power Ziflow! The API is a RESTful interface, essentially providing programmatic access to the features and data in the system. If you’ve interacted with a . The API exposes 95 endpoints secured with apiKey, basic, bearer authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Ziflow API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ziflow 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%2Fziflow.com%2Fziflow" | 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%2Fziflow.com%2Fziflow" | 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 Ziflow API.

Create New Proof

Get Proofs

Search Proofs

Update an Existing Proof

Delete Proof

Use Cases

Patterns agents use Ziflow API for, with concrete tasks.

GET STARTED

Start building with Ziflow API

Explore with Jentic One

View OpenAPI Document

Automated PROOFS Management

Automate proofs operations by combining multiple Ziflow API endpoints. Agents can get proofs and then search proofs in a single workflow.

Call GET /proofs to get proofs, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Ziflow API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic, bearer tokens manually.

Search Jentic for 'create new proof', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

95 endpoints — welcome to the ziflow api the ziflow api is built to allow you to easily and quickly embed ziflow’s proofing features in your own application or create an integration between ziflow and any other application.

METHOD

PATH

DESCRIPTION

POST

/proofs

Create New Proof

GET

/proofs

Get Proofs

POST

/proofs/search

Search Proofs

POST

/proofs/search/activity

Search Proofs Activity

GET

/proofs/{id}

Get Proof by ID

PUT

/proofs/{id}

Update an Existing Proof

DELETE

/proofs/{id}

Delete Proof

POST

/proofs/{id}/integration-properties

Add Integration Properties

POST

/proofs

Create New Proof

GET

/proofs

Get Proofs

POST

/proofs/search

Search Proofs

POST

/proofs/search/activity

Search Proofs Activity

GET

/proofs/{id}

Get Proof by ID

PUT

/proofs/{id}

Update an Existing Proof

DELETE

/proofs/{id}

Delete Proof

POST

/proofs/{id}/integration-properties

Add Integration Properties

Why Jentic?

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

Setup

Wiring Ziflow by hand means picking one of its several auth styles, bearer, basic, or an apikey header or query parameter, and pointing requests at the api.ziflow.io host yourself. Through Jentic you install once, import Ziflow from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Ziflow puts the proof id in the URL path (/proofs/{id}), so a rule can pin your agent to one proof: it can read and update that proof and nothing else. You choose the operations it may call, so destructive ones like proof deletion are not included unless you add them.

Credential isolation

Your Ziflow credential 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 'create a new proof' or 'search proof activity', and Jentic returns the matching Ziflow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Ziflow API through Jentic.

What authentication does the Ziflow API use?

The Ziflow API uses apiKey, basic, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create new proof with the Ziflow API?

Yes. Use the POST /proofs endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Ziflow API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create new proof through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create new proof'. Jentic returns the matching Ziflow API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Ziflow API have?

The Ziflow API exposes 95 endpoints covering proofs, stages, reviewers operations.

Can I limit what my agent is allowed to do with the Ziflow API?

Yes. Because Jentic One is self-hosted, you set the rules, and Ziflow puts the proof id directly in the URL path (/proofs/{id}), so you can pin your agent to a single proof and let it read and update only that proof. You choose exactly which operations the agent may call, so destructive endpoints like DELETE /proofs/{id} stay off unless you explicitly add them. The stored credential is injected at execution time and never enters the agent's prompt or context, so the agent operates only within the operations you allow.

Ziflow API

Connect the Ziflow API to your agent

Capabilities

Use Cases

Start building with Ziflow API

Key Endpoints

Why Jentic?

Related APIs

FAQs