Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer26 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: I need to create a new customer in Hiflow, I want to draft an estimate for a client, Generate an invoice from an approved estimate, List all open jobs for the current account
Not supported: Does not handle bank reconciliation, tax filing, or payroll - use for project, estimate, invoice, and timesheet management within a Hiflow account only.
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.
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.
1
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%2Fhiflow.net%2Fhiflow" | sh2
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%2Fhiflow.net%2Fhiflow" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Issue invoices and pull historic invoice records from /invoice for billing reconciliation
Track jobs and the tasks underneath them so agents can report on project progress
Log timesheet entries and tracker activity to capture billable hours per job
Pull activity and report endpoints to summarise team workload over a period
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
Login to obtain a JWT bearer token
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
Login to obtain a JWT bearer token
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
H
Hiflow API
- AI-Aware (B+)68/100
79
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability75
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
79
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
68%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Hiflow API by hand means logging in for a JWT, refreshing it through /login/requesttoken, sending it as a bearer token, and templating your account subdomain into the host. Through Jentic you install once, import the Hiflow API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Hiflow carries the target in the request body for its create operations, so scoping stays at the operation level: limit the agent to the operations it needs, such as creating an estimate or reading customers. You choose that set, so a broader operation like creating an invoice or a job is only available if you include it.
Credential isolation
Your Hiflow login credentials and the resulting JWT are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an invoice in Hiflow', and Jentic returns the matching Hiflow operation with its input schema so the agent calls POST /invoice without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Hiflow API?
Yes. Because you run Jentic One yourself, your own rules decide which Hiflow operations and credentials the agent can use, and scoping happens at the operation level since Hiflow carries the target in each request body. You choose the exact set the agent may call, for example reading customers with GET /customer and drafting quotes with POST /estimate, while leaving broader actions like issuing an invoice with POST /invoice or creating a job with POST /job out unless you include them. The stored Hiflow login credentials and JWT are injected only for the operations you permit.
GET STARTED