Install Jentic One Beta

Connect the Billberry API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Billberry 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbillberry.ee%2Fbillberry" | sh

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%2Fbillberry.ee%2Fbillberry" | 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 Billberry API.

Submit a structured electronic invoice for delivery to a recipient organization

List and retrieve received invoices, including a single invoice by its invoice id

Track invoice acknowledgements for both individual invoices and the acknowledgement feed

Resolve organizations by country code and registry code for invoice addressing

Manage partner-owned organizations and their sessions for delegated invoicing

GET STARTED

Start building with Billberry API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Billberry API for, with concrete tasks.

★ AI agent invoice submission

An AI finance agent needs to issue a compliant electronic invoice to a customer without a human logging into a portal. Through Jentic the agent calls the Billberry API to submit the invoice, then reads back the received-invoice and acknowledgement records to confirm delivery. Because Billberry addresses organizations by country and registry code, the agent can resolve the recipient before submitting and avoid misrouted invoices.

Search Jentic for 'submit an electronic invoice', resolve the recipient with GET /countries/{countryCode}/organizations, then call POST /invoices to send the invoice.

Received-invoice reconciliation

An accounts-payable workflow needs to pull invoices as they arrive on the network and match them against purchase orders. The received-invoices list and the single-invoice lookup return each invoice as a structured record, and the acknowledgements endpoints confirm receipt. This lets the workflow reconcile incoming invoices without manual data entry.

Call GET /invoices/received to list new invoices, then call GET /invoices/{invoiceId} for each and record the acknowledgement from GET /invoices/{invoiceId}/acknowledgements.

Organization directory resolution

Before invoicing, a workflow needs to confirm a counterparty exists and resolve its network identifier. The organization lookups resolve organizations by country and registry code, so a workflow can validate a recipient's registry code and route an invoice to the correct organization. This prevents invoices from failing addressing checks on submission.

Call GET /countries/{countryCode}/organizations/{registryCode} to resolve the recipient organization before submitting an invoice to it.

Delegated partner invoicing

An accounting platform acting as a partner needs to send and read invoices on behalf of the organizations it manages. The per-partner invoice and organization endpoints scope operations to a specific managed organization, and the session endpoints establish delegated access. This lets a platform automate invoicing across many client organizations from one integration.

Call POST /partners/{partnerId}/invoices to submit an invoice for a managed organization, then call GET /partners/{partnerId}/invoices/received to confirm delivery on its behalf.

Key Endpoints

32 endpoints — the billberry api sends and receives structured electronic invoices between organizations on the estonian and european e-invoicing network.

METHOD

PATH

DESCRIPTION

POST

/invoices

Submit an electronic invoice

GET

/invoices/received

List received invoices

GET

/invoices/{invoiceId}

Retrieve an invoice by id

GET

/invoices/{invoiceId}/acknowledgements

List acknowledgements for an invoice

GET

/invoice-acknowledgements

Read the acknowledgement feed

GET

/countries/{countryCode}/organizations

List organizations by country

POST

/partners/{partnerId}/invoices

Submit an invoice for a partner organization

POST

/invoices

Submit an electronic invoice

GET

/invoices/received

List received invoices

GET

/invoices/{invoiceId}

Retrieve an invoice by id

GET

/invoices/{invoiceId}/acknowledgements

List acknowledgements for an invoice

GET

/invoice-acknowledgements

Read the acknowledgement feed

GET

/countries/{countryCode}/organizations

List organizations by country

POST

/partners/{partnerId}/invoices

Submit an invoice for a partner organization

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Billberry API by hand means setting up its HTTP basic session credential and handling organization resolution before every submission yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Billberry API exposes invoice-exchange and organization operations, so a rule bounds which of them the agent may call: reading received invoices and acknowledgements, without invoice submission or partner-organization management unless you add them. You choose the allowed set, so the agent only runs the operations you pick.

Credential isolation

Your Billberry basic credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit an electronic invoice' or 'resolve an organization by registry code', and Jentic returns the matching Billberry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Billberry API through Jentic.

Is there a Billberry API MCP server?

You don't need an MCP server to give your agent the Billberry API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent submits and retrieves invoices on demand without loading another server's tool definitions into its context.

What authentication does the Billberry API use?

The Billberry API authenticates with HTTP basic authentication over a session credential, per its OpenAPI spec. When you call it through Jentic, that basic credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never appears in the agent's prompt or logs.

Can I submit an electronic invoice with the Billberry API?

Yes. The POST /invoices endpoint submits a structured electronic invoice for delivery to a recipient organization, and you can confirm delivery by reading the acknowledgements from GET /invoices/{invoiceId}/acknowledgements once the invoice is processed.

What are the rate limits for the Billberry API?

The OpenAPI spec does not specify rate limits for the Billberry API. Check the provider's documentation at https://billberry.ee for current limits, and note that invoice submission is an event-driven operation rather than something you would poll at high frequency.

How do I send an invoice through Jentic?

Search Jentic for 'submit an electronic invoice', load the matching operation, resolve the recipient with GET /countries/{countryCode}/organizations, and call POST /invoices to send it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Billberry API?

Yes. Because Jentic One is self-hosted, you decide which operations the agent may call: you might allow reading received invoices and acknowledgements while leaving out invoice submission or the partner-organization management operations, and every call the agent makes is logged.

Billberry Ee Billberry API

Name: Billberry API
Brand: Billberry API
Availability: InStock

Community OpenAPI document · agent-readyFinanceAccountingbasic32 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Exchange electronic invoices: submit and retrieve invoices, handle acknowledgements, and resolve organizations by country and registry code across the e-invoicing network.

Use for: I need to submit an e-invoice to a customer organization, Retrieve a received invoice by its invoice id, List all invoices received on the network, Check the acknowledgements recorded for a submitted invoice

Not supported: Does not handle payment execution, bank reconciliation, or tax filing. Use for e-invoice exchange and organization resolution only.

The Billberry API sends and receives structured electronic invoices between organizations on the Estonian and European e-invoicing network. It submits new invoices, lists and retrieves received invoices, and returns each invoice as a structured record so an agent can process it programmatically. It also handles invoice acknowledgements, resolves organizations by country and registry code, and lets a partner act on behalf of the organizations it manages through per-partner invoice and organization endpoints. The surface is built around invoice exchange and organization identity rather than ledgers or payment execution, making it the transport layer for compliant e-invoicing.

Jentic One on Github View OpenAPI Document

Connect the Billberry API to your agent

Capabilities

Start building with Billberry API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Billberry Ee Billberry API