Envoice In Envoice API

Name: Envoice API
Brand: Envoice API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingapiKey61 EndpointsREST

For Agents

Create and manage clients, estimates, invoices, items, and payments inside the Envoice billing platform and subscribe to invoice-activity webhooks.

Install Jentic One Beta

Connect the Envoice API to your agent

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

List, create, update, and delete clients in the Envoice billing system

Create and update estimates and convert an accepted estimate into an invoice

Send estimates and invoices to clients with /sendtoclient style endpoints

GET STARTED

Start building with Envoice API

Explore with Jentic

View OpenAPI Document

Envoice is a small-business invoicing and billing platform that handles clients, estimates, invoices, recurring invoices, payments, items, and reporting. The API exposes 61 endpoints covering the full invoicing lifecycle: client management, estimation creation and conversion to invoice, invoice issuing and payment recording, item and tax catalogues, and webhook subscriptions for invoice activity. Suited to SaaS apps and accounting integrations that need to push invoices into Envoice or react when an invoice is paid or sent to a client.

Use Cases

Patterns agents use Envoice API for, with concrete tasks.

★ SaaS Subscription Billing

A SaaS product creates a client in Envoice when a customer signs up, then schedules a recurring invoice via the recurring-invoice endpoints to bill on the subscription cadence. Payments are recorded back via the payment endpoints, and webhook notifications keep the application aware of paid, sent, and viewed events. Replaces a custom billing engine for SMB-facing SaaS.

Call POST /api/client/new for the new customer, then create a recurring invoice that bills monthly on day 1.

Estimate-to-Invoice Workflow

Sales teams create estimates with POST /api/estimation/new, send them via POST /api/estimation/sendtoclient, and convert accepted estimates into invoices with POST /api/estimation/convert. The conversion preserves line items and tax handling, eliminating double entry. Useful for project-based and services businesses.

Submit POST /api/estimation/sendtoclient for estimate 9001, then call POST /api/estimation/convert when the client accepts.

Invoice Activity Notifications

External systems subscribe to Envoice webhooks so dashboards and Slack channels react when invoices are sent, viewed, or paid. The webhook payload includes the invoice identifier and activity type, enabling fine-grained automation such as triggering a follow-up email if an invoice has been viewed but not paid for several days.

Register a webhook URL via the webhook subscription endpoint and verify the test payload arrives at the configured endpoint.

AI Agent Billing Assistant Through Jentic

An AI assistant uses Jentic to discover Envoice operations by intent and answers user questions like 'create an invoice for $1,200 to Acme for consulting' by chaining client lookup, item creation, and invoice issuing. The Envoice x-auth-key and x-auth-secret stay in the Jentic vault and never enter the agent's prompt context.

Search Jentic for 'create an invoice for a client', load the new-invoice endpoint, and execute it with the client ID and a single line item.

Key Endpoints

61 endpoints — envoice is a small-business invoicing and billing platform that handles clients, estimates, invoices, recurring invoices, payments, items, and reporting.

METHOD

PATH

DESCRIPTION

GET

/api/client/all

List all clients

POST

/api/client/new

Create a new client

POST

/api/client/update

Update an existing client

POST

/api/estimation/new

Create a new estimate

POST

/api/estimation/sendtoclient

Send an estimate to the client

POST

/api/estimation/convert

Convert an estimate into an invoice

GET

/api/estimation/all

List all estimates

POST

/api/estimation/changestatus

Change the status of an estimate

GET

/api/client/all

List all clients

POST

/api/client/new

Create a new client

POST

/api/client/update

Update an existing client

POST

/api/estimation/new

Create a new estimate

POST

/api/estimation/sendtoclient

Send an estimate to the client

Why Jentic?

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

Credential isolation

Envoice x-auth-key and x-auth-secret are stored encrypted in the Jentic vault (MAXsystem). Agents call /api/client/new, /api/estimation/convert, and the invoice endpoints through scoped tokens — neither header value is ever visible to the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create an invoice in Envoice') and receive the matching operation with its input schema, so the agent calls the correct /api/* path without parsing the docs site.

Time to first call

Direct Envoice integration: 2-3 days to wire up dual-header auth, the estimate-to-invoice flow, recurring schedules, and webhook receivers. Through Jentic: about an hour — search, load, execute.

FAQs

Specific to using Envoice API through Jentic.

What authentication does the Envoice API use?

The Envoice API uses two API keys: x-auth-key and x-auth-secret, both passed as headers on every request. Through Jentic, both values are stored encrypted in the vault (MAXsystem) and injected at execution time so they never enter the agent context.

Can I create a recurring invoice with the Envoice API?

Yes. The API exposes recurring-invoice endpoints to create, update, and pause recurring schedules so a SaaS application can hand subscription billing to Envoice rather than building its own engine.

How do I convert an estimate into an invoice?

Call POST /api/estimation/convert with the estimate identifier. The conversion carries over line items and tax treatment so there is no double entry. Pair with POST /api/estimation/sendtoclient to send the estimate to the client first.

What are the rate limits for the Envoice API?

The OpenAPI spec does not publish numeric rate limits. Envoice applies fair-use throttling at the account level. If you are running bulk imports or back-fills, contact Envoice support before sustained high-throughput operations.

How do I create a new invoice through Jentic?

Search Jentic for 'create an invoice in Envoice', load the new-invoice operation, and execute it with the client ID and line items. Get started at https://app.jentic.com/sign-up.

Does Envoice support webhooks?

Yes. Configure up to ten webhook URLs that receive HTTP POST payloads when invoice activity occurs (sent, viewed, paid). Endpoints that fail to return 200 across multiple retries are deactivated until they recover.

Envoice In Envoice API

Connect the Envoice API to your agent

Capabilities

Start building with Envoice API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs