Bokio Se Bokio API

Name: Bokio API
Brand: Bokio API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingoauth2, bearer34 EndpointsREST

For Agents

Post journal entries, create and publish invoices, manage customers and items, and upload receipts in a Bokio accounting workspace.

Install Jentic One Beta

Connect the Bokio API to your agent

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

Post a journal entry to the Bokio ledger and reverse it if a correction is needed

Create and publish a customer invoice, then record payments and settlements against it

Upload a receipt or supporting document and attach it to bookkeeping records

GET STARTED

Start building with Bokio API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Bokio API for, with concrete tasks.

★ Automated Invoicing for SaaS Subscriptions

Generate Bokio invoices automatically when a Swedish customer is billed in your application, attach the line items, and publish so the invoice is sent and booked. The /invoices endpoints create, update, and publish invoices, and /invoices/{invoiceId}/payments records settlement when the customer pays. Removes the manual data entry that small Swedish businesses typically do at month end.

POST /invoices for customer 9241 with two line items totalling 4500 SEK, then POST /invoices/{invoiceId}/publish

Receipt Upload and Attachment

Capture supplier receipts from email or a mobile app and push them into Bokio so they are stored alongside the journal entry that records the expense. The /uploads endpoint accepts the file, and the resulting upload ID can be referenced when posting the journal entry. Helps Swedish bookkeepers comply with the digital archive requirement.

POST /uploads with the receipt PDF, then POST /journal-entries referencing the returned upload ID

Bank Reconciliation Workflow

Pull invoices, post matching payments, and create settlements as bank transactions arrive so the ledger stays current. Combine /invoices, /invoices/{invoiceId}/payments, and /invoices/{invoiceId}/settlements to close out receivables. Useful for finance teams that want continuous reconciliation rather than a month-end batch.

POST /invoices/{invoiceId}/payments with amount 1200 SEK and date 2026-06-01 for invoice 8821

AI Agent Bookkeeping Assistant

An AI agent uses Jentic to discover Bokio operations from natural-language requests, creates invoices, posts journal entries, and uploads receipts on behalf of a Swedish small business. Credentials are isolated in your Jentic One instance so the OAuth refresh token never reaches the prompt. The agent runs the search-load-execute cycle for each accounting action.

Search Jentic for 'create an invoice in Bokio', load the operation, and execute it with the customer ID and line items

Key Endpoints

34 endpoints — jentic publishes the only available openapi specification for bokio api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/invoices

Create an invoice

POST

/invoices/{invoiceId}/publish

Publish an invoice so it is issued and booked

POST

/invoices/{invoiceId}/payments

Record a payment against an invoice

POST

/journal-entries

Post a journal entry to the ledger

POST

/journal-entries/{journalId}/reverse

Reverse a posted journal entry

POST

/uploads

Add a receipt or supporting document upload

GET

/chart-of-accounts

Read the company chart of accounts

POST

/invoices

Create an invoice

POST

/invoices/{invoiceId}/publish

Publish an invoice so it is issued and booked

POST

/invoices/{invoiceId}/payments

Record a payment against an invoice

POST

/journal-entries

Post a journal entry to the ledger

POST

/journal-entries/{journalId}/reverse

Reverse a posted journal entry

Why Jentic?

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

Credential isolation

Your Bokio OAuth refresh token is stored once, encrypted, by your own Jentic One instance, which mints short-lived bearer tokens at execution time. The refresh token never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an invoice in Bokio' or 'post a journal entry', and Jentic returns the matching Bokio operation with its input schema so the agent calls the right endpoint without browsing the Bokio docs.

Time to first call

FAQs

Specific to using Bokio API through Jentic.

Why is there no official OpenAPI spec for Bokio API?

Bokio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bokio API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Bokio API use?

Bokio supports OAuth 2.0 authorization code flow at /authorization/authorize and /authorization/token, plus HTTP Bearer for the resulting access token. Through Jentic the refresh token lives in the encrypted vault and the agent only ever sees a scoped, short-lived bearer.

Can I create and publish invoices with the Bokio API?

Yes. POST /invoices to create the invoice, POST /invoices/{invoiceId}/line-items to add lines, then POST /invoices/{invoiceId}/publish to issue it. You can also record payments via POST /invoices/{invoiceId}/payments.

How do I post a journal entry through Jentic?

Search Jentic for 'post a journal entry in Bokio', load the POST /journal-entries operation schema, then execute it with the entry lines. If you need to reverse it later, use POST /journal-entries/{journalId}/reverse.

What are the rate limits for the Bokio API?

The OpenAPI spec does not declare formal rate limits. Bokio's documentation at docs.bokio.se outlines fair-use guidance - back off on HTTP 429 responses and avoid tight polling loops on /invoices and /journal-entries.

Can I attach receipts to bookkeeping entries?

Yes. POST /uploads with the receipt file to get an upload ID, then reference that ID when creating the related journal entry. The uploaded file can be retrieved later via GET /uploads/{uploadId}/download.

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

Yes. Because you host Jentic One yourself, your own rules decide which Bokio operations and credentials the agent may use, so you can grant read-only access to the chart of accounts while withholding writes. Since Bokio puts the invoice and journal IDs in the URL path, such as /invoices/{invoiceId}/publish and /journal-entries/{journalId}/reverse, a rule can pin the agent to acting on a specific invoice or entry. Reversing a journal entry through POST /journal-entries/{journalId}/reverse stays off limits unless you explicitly add it to the allowed set.

Bokio Se Bokio API

Connect the Bokio API to your agent

Capabilities

Start building with Bokio API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs