canonical: https://jentic.com/apis/pleo.io/pleo # Pleo Bookkeeping Core API Bookkeeping Core OpenAPI definitions. The API exposes 5 endpoints secured with bearer authentication. ## For AI agents Programmatically create a new account., retrieves an account in pleo by its id.. Covers 5 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a new account.', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | 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 | ## Key resources - **BookkeepingCore** — This resource is associated with the BookkeepingCore API - **Accounts** — This API enables you to create an account in Pleo, search for an account by its specific ID, update - **Aggregated Bookkeeping Category Groups** — This API enables you to read aggregated bookkeeping category groups. 💡**Note** Please note that on - **Bookkeeping Categories** — This API enables you to perform operations on a bookkeeping category. 💡**Note** Please note that o - **Bookkeeping Category Groups** — This API enables you to perform operations on a bookkeeping category group. 💡**Note** Please note ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 72 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 66 / 100 - AI-Readiness & Agent Experience: 57 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 73 / 100 - **View full report:** https://jentic.com/apis/pleo.io/pleo/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Pleo Bookkeeping Core API by hand means learning its bearer auth, choosing between the production and staging hosts, and hand-building requests across its account endpoints yourself. Through Jentic you install once, import Pleo from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Pleo puts the account id in the URL path (`/v1-beta/accounts/{accountId}`), so a rule can pin your agent to one account: it reads and updates that account and nothing else. You choose the operations it may call, so destructive ones like deleting an account are not included unless you add them. - **Credential handling:** Your Pleo token 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. - **Discovery method:** Agents search Jentic by intent such as 'create a new account' or 'search accounts', and Jentic returns the matching Pleo operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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. ### Can I limit what my agent is allowed to do with the Pleo Bookkeeping Core API? Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and you pick exactly which Bookkeeping Core operations it can call. Since Pleo puts the account ID in the URL path (`/v1-beta/accounts/{accountId}`), a rule can pin the agent to a single account so it only reads and updates that account and nothing else. Destructive calls like DELETE `/v1-beta/accounts/{accountId}` stay off limits unless you explicitly grant them.