Hubflo
Hubflo is a client portal platform for service businesses — consultants, agencies, accountants, and professional-service firms — bringing client onboarding, messaging, document management, e-signatures, forms, proposals, invoicing, tasks, and project collaboration into one branded workspace. Hubflo exposes a REST API (v2) at app.hubflo.com/api/v2 with bearer-token authentication, JSON request/response bodies, UUID resource identifiers, page-based pagination, a 1000 request/minute rate limit, and a native webhook system spanning 29 event types across companies, contacts, workspaces, invoices, forms, tasks, and e-signature submissions. Hubflo also publishes official TypeScript and MCP-server packages and a hosted remote MCP server. Backed by Seedcamp.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Hubflo the way a machine reads it — 34 machine-readable artifacts across 28 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Hubflo scores 50.2/100 (developing), with a separate agent-readiness read of 82/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hubflo
Each block below is one kind of artifact we hold for Hubflo. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Hubflo chat_room API
The chat_room API from Hubflo — 4 operation(s) for chat_room.
Hubflo comment API
The comment API from Hubflo — 2 operation(s) for comment.
Hubflo company API
The company API from Hubflo — 2 operation(s) for company.
Hubflo contact API
The contact API from Hubflo — 4 operation(s) for contact.
Hubflo custom_field API
The custom_field API from Hubflo — 2 operation(s) for custom_field.
Hubflo custom_field_value API
The custom_field_value API from Hubflo — 1 operation(s) for custom_field_value.
Hubflo folder API
The folder API from Hubflo — 1 operation(s) for folder.
Hubflo form API
The form API from Hubflo — 17 operation(s) for form.
Hubflo invoice API
The invoice API from Hubflo — 8 operation(s) for invoice.
Hubflo invoicing_profile API
The invoicing_profile API from Hubflo — 2 operation(s) for invoicing_profile.
Hubflo item API
The item API from Hubflo — 1 operation(s) for item.
Hubflo member API
The member API from Hubflo — 1 operation(s) for member.
Hubflo message API
The message API from Hubflo — 1 operation(s) for message.
Hubflo note API
The note API from Hubflo — 2 operation(s) for note.
Hubflo organizations API
The organizations API from Hubflo — 3 operation(s) for organizations.
Hubflo ping API
The ping API from Hubflo — 1 operation(s) for ping.
Hubflo portals API
The portals API from Hubflo — 1 operation(s) for portals.
Hubflo project API
The project API from Hubflo — 5 operation(s) for project.
Hubflo project_section API
The project_section API from Hubflo — 3 operation(s) for project_section.
Hubflo project_type API
The project_type API from Hubflo — 2 operation(s) for project_type.
Hubflo proposal API
The proposal API from Hubflo — 6 operation(s) for proposal.
Hubflo smartdoc API
The smartdoc API from Hubflo — 5 operation(s) for smartdoc.
Hubflo tag API
The tag API from Hubflo — 2 operation(s) for tag.
Hubflo task API
The task API from Hubflo — 6 operation(s) for task.
Hubflo task_template API
The task_template API from Hubflo — 5 operation(s) for task_template.
Hubflo time_tracking API
The time_tracking API from Hubflo — 2 operation(s) for time_tracking.
Hubflo webhook API
The webhook API from Hubflo — 4 operation(s) for webhook.
Hubflo workspace API
The workspace API from Hubflo — 24 operation(s) for workspace.
Scroll within the panel for all 28 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
hubflo-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hubflo Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Hubflo Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Hubflo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hubflo · machine-readable index on apis.io