Hiflow API

Name: Hiflow API
Brand: Hiflow API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer26 EndpointsREST

For Agents

Manage customers, estimates, invoices, jobs, tasks, and timesheets in a Hiflow account. Authenticates with a JWT bearer token requested via the login endpoint.

Install Jentic One Beta

Connect the Hiflow API to your agent

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

Authenticate against a Hiflow account and request a fresh JWT via /login and /login/requesttoken

Create, update, and list customer records with full CRUD on /customer and /customer/{id}

Draft and revise client estimates through /estimate before converting them to invoices

GET STARTED

Start building with Hiflow API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Hiflow API, keeping it validated and agent-ready. Hiflow is a French project and service management platform that lets freelancers and small agencies track customers, jobs, estimates, invoices, timesheets, and activity in one place. The API exposes 26 endpoints across customers, estimates, invoices, jobs, tasks, timesheets, trackers, users, and reports, all secured with a JWT bearer token obtained through a login operation. Agents can use it to automate quoting, invoicing, and time tracking workflows tied to a specific Hiflow account subdomain.

Use Cases

Patterns agents use Hiflow API for, with concrete tasks.

★ Freelancer Quote-to-Invoice Automation

Freelancers and small agencies use Hiflow to move from a client enquiry to a paid invoice without leaving the platform. Agents can create the customer, draft an estimate via /estimate, convert accepted estimates into invoices via /invoice, and track payment status. The 26-endpoint surface covers the full lifecycle for a single Hiflow account subdomain.

Create a customer record for Acme Ltd, draft an estimate for two consulting days at 800 EUR each, and on acceptance issue the corresponding invoice via /invoice.

Project Time Tracking and Reporting

Agencies bill by the hour and need accurate timesheet records per job. Hiflow exposes /job, /timesheet, and /tracker endpoints so an agent can open a job, log time as it is worked, and pull /reports to produce a weekly utilisation summary. This avoids a separate time-tracking tool and keeps billable hours linked to the invoiceable job record.

Log 4.5 hours against job ID 1287 for today and then retrieve the weekly activity report for the current user.

Customer Data Sync to External CRM

Teams running a separate CRM alongside Hiflow need customer data to stay aligned. Agents can list customers via GET /customer, diff against the CRM, and use POST or PUT /customer to push corrections back. Because the API requires a JWT issued per Hiflow subdomain, credential isolation per account is straightforward.

List all Hiflow customers modified since yesterday and upsert each one into the connected CRM.

AI Agent Bookkeeping Assistant

An AI agent can act as a back-office assistant for a freelancer using Hiflow. Through Jentic, the agent searches for an operation by intent, loads the JSON schema, and executes the call with the user's vault-stored Hiflow JWT. Common tasks include drafting invoices from a chat prompt, chasing unpaid invoices, and summarising the previous month's activity.

When the user says 'invoice Acme for last week', search Jentic for 'create invoice in Hiflow', load the schema, and execute POST /invoice with the matched line items.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/login

POST

/login/requesttoken

Request a refreshed JWT token

GET

/customer

List customer records

POST

/customer

Create a customer

POST

/estimate

Create an estimate

POST

/invoice

Create an invoice

POST

/job

Create a job

POST

/login

POST

/login/requesttoken

Request a refreshed JWT token

GET

/customer

List customer records

POST

/customer

Create a customer

POST

/estimate

Create an estimate

POST

Why Jentic?

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

Credential isolation

Hiflow login credentials and the resulting JWT are stored encrypted in the Jentic vault (MAXsystem). The agent receives a scoped session token; raw passwords never enter the agent context, and the JWT is refreshed via /login/requesttoken automatically.

Intent-based discovery

Agents search by intent (e.g., 'create an invoice in Hiflow') and Jentic returns the matching Hiflow operation with its input schema, so the agent can call POST /invoice without browsing docs.

Time to first call

Direct Hiflow integration: 1-3 days handling JWT login, refresh, and per-account base URL. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Hiflow API through Jentic.

Why is there no official OpenAPI spec for Hiflow API?

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

The Hiflow API uses HTTP bearer authentication with a JWT. Call POST /login with your Hiflow credentials to receive a token, then send it in the Authorization header on every other request. Through Jentic, your Hiflow credentials are stored in the MAXsystem vault and the JWT is fetched and rotated for the agent automatically.

Can I create invoices and estimates through the Hiflow API?

Yes. POST /estimate creates a client estimate and POST /invoice issues an invoice; both can be retrieved with the corresponding GET endpoints and updated via PUT. Estimates are typically created first and then converted into invoices once the client accepts.

What are the rate limits for the Hiflow API?

The Hiflow OpenAPI specification does not declare rate limits. Hiflow is a per-account hosted product, so practical limits are tied to your account plan. Build retry-with-backoff into long-running sync jobs and consult Hiflow support for the limits applied to your subdomain.

How do I list a customer's invoices through Jentic?

Search Jentic for 'list Hiflow invoices', load the schema for GET /invoice, and execute the call with the customer filter. Example: pip install jentic, then await client.search('list invoices in Hiflow') followed by client.execute() with the returned operation id.

Does the Hiflow API support multiple accounts?

Yes. The base URL contains a {account} placeholder so each Hiflow subdomain has its own host. Configure the account value alongside the JWT when registering credentials in Jentic so the agent calls the correct tenant.

Hiflow API

Connect the Hiflow API to your agent

Capabilities

Start building with Hiflow API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs