Pleo Bookkeeping Core API
✓ Official Vendor SpecDeveloper ToolsSource Controlbearer5 EndpointsREST
For Agents
Programmatically create a new account., retrieves an account in pleo by its id.. Covers 5 operations with bearer authentication.
Use for: I need to a new account., I want to retrieves an account in pleo by its id., Search for an account, Find all an account
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Bookkeeping Core OpenAPI definitions. The API exposes 5 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Bookkeeping Core API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bookkeeping Core 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Bookkeeping Core API.
Create a new account.
Retrieves an account in Pleo by its ID.
Update an account
Delete an account
Fetch a list of accounts
Use Cases
Patterns agents use Bookkeeping Core API for, with concrete tasks.
★ Developer Tools Operations
Use the Bookkeeping Core API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including create a new account., retrieves an account in pleo by its id., update an account.
Call POST /v1-beta/accounts to create a new account.
Automated BookkeepingCore Management
Automate bookkeepingcore operations by combining multiple Bookkeeping Core API endpoints. Agents can retrieves an account in pleo by its id. and then update an account in a single workflow.
Call GET /v1-beta/accounts/{accountId} to retrieves an account in pleo by its id., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Bookkeeping Core API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create a new account.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
5 endpoints — bookkeeping core openapi definitions.
METHOD
PATH
DESCRIPTION
POST
/v1-beta/accounts
Create a new account.
GET
/v1-beta/accounts/{accountId}
Retrieves an account in Pleo by its ID.
PUT
/v1-beta/accounts/{accountId}
Update an account
DELETE
/v1-beta/accounts/{accountId}
Delete an account
POST
/v1-beta/accounts:search
Fetch a list of accounts
POST
/v1-beta/accounts
Create a new account.
GET
/v1-beta/accounts/{accountId}
Retrieves an account in Pleo by its ID.
PUT
/v1-beta/accounts/{accountId}
Update an account
DELETE
/v1-beta/accounts/{accountId}
Delete an account
POST
/v1-beta/accounts:search
Fetch a list of accounts
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Bookkeeping Core API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a new account.') and Jentic returns the matching Bookkeeping Core API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Bookkeeping Core API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Bookkeeping Core API through Jentic.
What authentication does the Bookkeeping Core API use?
The Bookkeeping Core API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create a new account. with the Bookkeeping Core API?
Yes. Use the POST /v1-beta/accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Bookkeeping Core API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new account. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new account.'. Jentic returns the matching Bookkeeping Core API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Bookkeeping Core API have?
The Bookkeeping Core API exposes 5 endpoints covering bookkeepingcore, accounts, aggregated bookkeeping category groups operations.
GET STARTED