Hiveage API
Official vendor OpenAPI document · agent-readyFinanceAccountingbasic31 EndpointsREST
For Agents
Issue invoices, track payments and expenses, and manage clients, contacts, items, and recurring billing in a Hiveage account.
Use for: I want to issue an invoice to a specific client, Record a partial payment against an existing invoice, List all overdue invoices for the current month, Create a recurring monthly invoice for a retainer
Not supported: Does not handle payment processing, tax filing, or full accounting general ledger - use for invoicing, estimates, and lightweight expense tracking only.
Hiveage is an online invoicing platform for small businesses and freelancers. The API exposes management of connections (clients), contacts, invoices, estimates, recurring invoices, payments, items, and expenses, all under a per-account subdomain. It is intended for service businesses that need to programmatically issue invoices, track payments, and manage client and item catalogs.
Install Jentic One Beta
Connect the Hiveage API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hiveage 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%2Fhiveage.com%2Fhiveage" | 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%2Fhiveage.com%2Fhiveage" | 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 Hiveage API.
Issue and manage invoices with line items, currency, and due dates
Send and update estimates that convert into invoices when accepted
Set up recurring invoices that bill clients on a schedule
Record payments against invoices and reconcile partial or full settlement
Manage connections (clients) and their associated contacts
Track expenses by category for reporting and reimbursement
Maintain a catalog of items used as invoice line entries
Use Cases
Patterns agents use Hiveage API for, with concrete tasks.
★ Automated Client Invoicing
Service businesses bill clients on agreed schedules and need to issue invoices reliably without manual entry. The Hiveage API supports invoice creation with line items, due dates, and currency, plus payment recording for reconciliation. Agents wire this into project completion or contract milestones so invoicing happens the moment work ships.
Create a Hiveage invoice for connection conn_123 with two line items totalling $2,400 and a 30-day due date.
Recurring Retainer Billing
Agencies on monthly retainers want billing to run itself. POST /recurrings sets up a recurring invoice with cadence and end date so Hiveage issues each invoice automatically. The agent can adjust amounts when scope changes mid-engagement, avoiding manual recreation each month.
Create a recurring invoice for connection conn_123 at $5,000 per month starting next billing cycle.
Payment Reconciliation
Bookkeepers reconcile bank deposits against invoices each week. The agent matches incoming bank amounts to open Hiveage invoices and posts payments via the payments endpoint, marking invoices as paid or partially paid. This compresses a multi-hour weekly task into minutes.
Record a $1,200 payment against invoice inv_789 dated today and verify the invoice status flips to paid or part-paid.
Agent-Run Billing Workflow
An AI finance agent connected via Jentic monitors completed projects, identifies billable milestones, issues the invoice, and notifies the client. The Hiveage basic auth credential stays in your Jentic One instance so the agent never holds the API key. End-to-end setup takes under an hour because operation schemas load on demand.
Identify completed projects since last billing run, issue Hiveage invoices for each, and report which invoices were created.
Key Endpoints
31 endpoints — hiveage is an online invoicing platform for small businesses and freelancers.
METHOD
PATH
DESCRIPTION
POST
/network
Create a connection (client)
POST
/invs
Create an invoice
POST
/network/{hashKey}/contacts
Create a contact for a connection
GET
/network
List all connections
POST
/network
Create a connection (client)
POST
/invs
Create an invoice
POST
/network/{hashKey}/contacts
Create a contact for a connection
GET
/network
List all connections
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Hiveage API by hand means sending your API key as Basic auth and templating your account subdomain into the host on every call. Through Jentic you install once, import the Hiveage API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Hiveage puts the network hash key in the URL path (/network/{hashKey}/contacts, /network/{hashKey}/invoices), so a rule can pin your agent to one network and the operations around it, such as issuing an invoice or adding a contact. You choose the operations it may call, so destructive ones like deleting a network or an invoice are not included unless you add them.
Credential isolation
Your Hiveage API key is stored once, encrypted, by your own Jentic One instance and injected as the Basic auth header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'issue an invoice to a client', and Jentic returns the matching Hiveage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe handles card payment collection that settles into Hiveage records
Choose Stripe to actually collect card payments; record the resulting payment against the corresponding Hiveage invoice.
FAQs
Specific to using Hiveage API through Jentic.
What authentication does the Hiveage API use?
Hiveage uses HTTP Basic Authentication: the API key is sent as the username and the password field is ignored. Through Jentic, the key is stored encrypted in your Jentic One instance and added to the Authorization header at execution time so the agent never reads the raw value.
Can I issue recurring invoices through the Hiveage API?
Yes. The recurring invoices resource lets you create a schedule (cadence, start date, optional end date) and amount; Hiveage issues each invoice automatically on schedule. Update the recurring entry when scope or pricing changes.
What is the base URL for the Hiveage API?
Hiveage uses an account-specific subdomain: https://{subdomain}.hiveage.com/api where {subdomain} is your Hiveage account name. Set the subdomain server variable when configuring the client. Through Jentic this is passed at execution time.
What are the rate limits for the Hiveage API?
Hiveage does not publish public rate limits. Treat the API as moderate-volume per account and back off on 429 responses; for batch invoicing keep request rates to a few per second per subdomain.
How do I record a payment against an invoice through Jentic?
Search Jentic for 'record invoice payment hiveage', load the payments POST operation, and execute with the invoice id and amount. Use pip install jentic and the async SearchRequest, LoadRequest, ExecutionRequest pattern.
Can I limit what my agent is allowed to do with the Hiveage API?
Yes. Because you self-host Jentic One, you write the rules that decide which Hiveage operations and credentials your agent may use. Hiveage carries the network hash key in the URL path, such as /network/{hashKey}/contacts and /network/{hashKey}/invoices, so you can pin the agent to a single network and the operations around it, like issuing an invoice or adding a contact. You choose which operations are exposed, so destructive calls such as deleting a network or an invoice stay off limits unless you add them.
GET STARTED