Fakturoid Cz Fakturoid API

Name: Fakturoid API
Brand: Fakturoid API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingbasic24 EndpointsREST

For Agents

Manage invoices, subjects, expenses, and recurring billing generators across a Fakturoid account. Useful for Czech-market invoicing automations and accounting integrations.

Install Jentic One Beta

Connect the Fakturoid API to your agent

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

Issue and update invoices for an account on Fakturoid

Search and filter invoices by status, subject, or issue date

Fire actions on an invoice such as marking it sent or paid

Manage subject (customer) records used on invoices and expenses

GET STARTED

Start building with Fakturoid API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Fakturoid API for, with concrete tasks.

★ Issue Invoice to a Czech Customer

A SaaS business invoicing a Czech customer creates the subject record, issues the invoice, and triggers the send action through three calls. The flow uses POST /accounts/{slug}/subjects.json to ensure the subject exists, POST /accounts/{slug}/invoices.json to create the invoice, and POST /accounts/{slug}/invoices/{id}/fire.json to mark it sent. Suited to subscription billing where invoices are issued on a fixed schedule.

POST the subject details to /accounts/{slug}/subjects.json, POST the invoice payload referencing that subject id to /accounts/{slug}/invoices.json, then POST to /accounts/{slug}/invoices/{id}/fire.json with the send event.

Unpaid Invoice Reconciliation

A finance team queries Fakturoid each morning for unpaid invoices, cross-references bank account transactions, and marks paid invoices through the fire action. The flow uses GET /accounts/{slug}/invoices/search.json to filter by status and POST .../fire.json to update state. Designed to run as a scheduled job over a small business's daily reconciliation window.

Call GET /accounts/{slug}/invoices/search.json with status=open, match each result against the bank account transactions, and fire the paid action on matching invoices.

Recurring Invoice Generator

A subscription product creates recurring invoice generators in Fakturoid so that monthly invoices are issued without further calls. The Generators endpoints under the spec maintain the recurring schedule, and each cycle creates a fresh invoice that can be searched and fired through the same v3 surface. Reduces operational overhead for businesses on monthly retainers.

Create a recurring generator under /accounts/{slug}/generators (per the Generators tag) with the subject id, line items, and recurrence rule, then poll /accounts/{slug}/invoices/search.json for the issued invoices each cycle.

Expense Logging from Receipts

An accounting integration logs expenses against the Fakturoid account when receipts are processed by a separate document scanner. The Expenses endpoint group covers create, list, and detail operations under /accounts/{slug}/expenses, and subjects are reused across invoices and expenses. Suited to bookkeepers running monthly expense imports.

POST each parsed receipt as an expense under /accounts/{slug}/expenses.json with the supplier subject id and the line item amounts.

AI Agent Bookkeeping Assistant

An AI agent assisting a Czech freelancer uses Jentic to look up overdue invoices, read recent events, and issue reminder invoices. Jentic exposes the 24 Fakturoid operations with their schemas and account-slug parameter, so the agent can answer 'who owes me money this week' or 'send invoice to ACME for 5000 CZK' without browsing the developer site.

Call jentic.search with 'find overdue invoices on Fakturoid', load /accounts/{slug}/invoices/search.json, and execute it with status=overdue, returning the invoice numbers and totals.

Key Endpoints

24 endpoints — fakturoid is a czech online invoicing application whose v3 api exposes invoicing, accounting subjects, expenses, recurring generators, todos, events, and bank accounts across 24 endpoints.

METHOD

PATH

DESCRIPTION

GET

/accounts/{slug}/invoices.json

List invoices for an account

POST

/accounts/{slug}/invoices.json

Create an invoice

GET

/accounts/{slug}/invoices/search.json

Search invoices by status, subject, or date

POST

/accounts/{slug}/invoices/{id}/fire.json

Trigger an action on an invoice

GET

/accounts/{slug}/subjects.json

List subjects (customers)

POST

/accounts/{slug}/subjects.json

Create a subject

GET

/accounts/{slug}/invoices.json

List invoices for an account

POST

/accounts/{slug}/invoices.json

Create an invoice

GET

/accounts/{slug}/invoices/search.json

Search invoices by status, subject, or date

POST

/accounts/{slug}/invoices/{id}/fire.json

Trigger an action on an invoice

GET

/accounts/{slug}/subjects.json

List subjects (customers)

Why Jentic?

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

Credential isolation

Fakturoid Basic auth credentials (email plus API token) are stored encrypted in the Jentic vault. Jentic constructs the Authorization header at request time, so the agent receives a scoped execution permission rather than the raw token.

Intent-based discovery

Agents search Jentic for invoicing intents (e.g. 'create invoice', 'search overdue invoices') and Jentic returns matching Fakturoid operations with their schemas and the account-slug parameter, so the agent calls the right endpoint without reading docs.

Time to first call

Direct integration: 1-2 days for Basic auth, slug routing, and search-pagination handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Fakturoid API through Jentic.

What authentication does the Fakturoid API use?

Fakturoid v3 uses HTTP Basic auth — the email and an API token are encoded in the Authorization header. Through Jentic both values are held in the vault and Jentic builds the Basic header at execution time so the credentials never enter the agent context.

Can I create an invoice with the Fakturoid API?

Yes. POST the invoice payload, including the subject id and line items, to /accounts/{slug}/invoices.json. Once created you can call /accounts/{slug}/invoices/{id}/fire.json to trigger send and pay actions on the invoice.

What are the rate limits for the Fakturoid API?

The OpenAPI spec does not declare numeric rate limits. Fakturoid applies fair-use throttling per account — keep batch operations sequential per account slug rather than firing parallel requests.

How do I search unpaid invoices through Jentic?

Run pip install jentic, call jentic.search with 'find overdue invoices on Fakturoid', and execute the returned /accounts/{slug}/invoices/search.json operation with status=overdue. The Basic auth credentials are replayed from the vault.

Does the Fakturoid API support recurring billing?

Yes. The Generators tag exposes operations to create and manage recurring invoice generators, which produce a new invoice on each cycle that can then be searched and fired through the regular invoice endpoints.

What is the account slug parameter used in every URL?

Every operation under /accounts/{slug} is scoped to a specific Fakturoid account by its slug — the value visible in the app URL after a user logs in. Pass it as a path parameter on every account-scoped call.

Fakturoid Cz Fakturoid API

Connect the Fakturoid API to your agent

Capabilities

Start building with Fakturoid API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs