Install Jentic One Beta

Connect the Dynamics 365 Business Central to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dynamics 365 Business Central, 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%2Fdynamics.com%2Fdynamics-365-business-central" | 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%2Fdynamics.com%2Fdynamics-365-business-central" | 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 Dynamics 365 Business Central API.

Read and create customers, vendors, and inventory items within a company

Create and post sales invoices, sales orders, quotes, and credit memos

Record journals, journal lines, and customer payments

Retrieve financial statements such as the balance sheet, cash flow statement, and aged receivables

GET STARTED

Start building with Dynamics 365 Business Central API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dynamics 365 Business Central API for, with concrete tasks.

★ Agent-driven bookkeeping

An AI agent connected through Jentic can keep a Business Central company's books moving: create a customer, raise and post a sales invoice, and record the payment when it arrives. Because every record is scoped to a company id in the path, the agent works within one company's ledgers and returns the posted invoice and payment so the operator has a confirmation trail.

Create a customer in a company, raise a sales invoice for it, and record a customer payment against that invoice.

Financial reporting

The API returns standard Business Central financial statements, including the balance sheet, cash flow statement, retained earnings, and aged accounts receivable and payable. A reporting agent can pull these statements for a company and summarize the figures, turning a month-end review into a scripted read rather than an export from the Business Central client.

Retrieve the balance sheet and aged accounts receivable for a company and summarize the top overdue balances.

Order-to-cash automation

Business Central models the full order-to-cash flow as sales quotes, sales orders, and sales invoices with their line items. An agent can create a sales quote, convert its contents into a sales order, and raise the resulting invoice, keeping the documents linked to the same customer within one company.

Create a sales quote for a customer, create the matching sales order, and raise a sales invoice for it.

Master-data synchronization

Customers, vendors, and items are the master data behind every transaction, and the API reads and writes all three per company. A sync agent can keep a company's customer and item lists aligned with an external system, creating or updating records so downstream invoicing and ordering use consistent data.

List the customers in a company, create any missing ones from an external list, and update item records that have changed.

Key Endpoints

324 endpoints — the dynamics 365 business central api exposes the standard financial and sales records of a business central company over rest.

METHOD

PATH

DESCRIPTION

GET

/companies

Returns a list of companies

GET

/companies({company_id})/customers

Returns a list of customers

POST

/companies({company_id})/customers

Create a customer

GET

/companies({company_id})/salesInvoices

Returns a list of sales invoices

POST

/companies({company_id})/salesInvoices

Create a sales invoice

GET

/companies({company_id})/items

Returns a list of items

POST

/companies({company_id})/items

Create an item

GET

/companies({company_id})/vendors

Returns a list of vendors

GET

/companies

Returns a list of companies

GET

/companies({company_id})/customers

Returns a list of customers

POST

/companies({company_id})/customers

Create a customer

GET

/companies({company_id})/salesInvoices

Returns a list of sales invoices

POST

/companies({company_id})/salesInvoices

Create a sales invoice

GET

/companies({company_id})/items

Returns a list of items

POST

/companies({company_id})/items

Create an item

GET

/companies({company_id})/vendors

Returns a list of vendors

Why Jentic?

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

Setup

Wiring Business Central by hand means registering an app in Microsoft's identity platform, running the oauth2 flow for the right resource scope, and learning its OData company-scoped URL shape across hundreds of endpoints. Through Jentic you install once, import Business Central from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Business Central puts the company id in the URL path, so a rule can pin your agent to one company and the endpoints you pick. You choose the operations it may call, so write operations such as posting invoices or deleting records are not included unless you add them.

Credential isolation

Your Business Central oauth2 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a sales invoice' or 'get the balance sheet', and Jentic returns the matching Business Central operation with its input schema so the agent calls the right endpoint without scanning the full OData surface.

FAQs

Specific to using Dynamics 365 Business Central API through Jentic.

What authentication does the Dynamics 365 Business Central API use?

The Business Central API authenticates with oauth2 against Microsoft's identity platform, per its OpenAPI spec, using the Business Central resource scope so the token can read and write financial data. You obtain the token from the Microsoft login endpoint and send it as a bearer token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

Is there a Dynamics 365 Business Central MCP server?

You don't need an MCP server to give your agent the Business Central API. Jentic connects it directly from the API Directory: import Business Central, store your oauth2 credential once, and your agent calls its operations. Because the API exposes hundreds of per-company endpoints, Jentic discovers the right operation on demand rather than loading every definition into the agent's context.

Can I limit what my agent is allowed to do with the Dynamics 365 Business Central API?

Yes. Write a rule that pins your agent to one company's id in the path and allows only the read operations, such as listing customers and reading the balance sheet, so it can report figures but cannot post invoices or delete records, and every call it makes is logged. Because the company id is part of the URL, the agent's reach is confined to the company you name.

Can I post a sales invoice with the Dynamics 365 Business Central API?

Yes. The sales invoice endpoints create invoices and their line items under a company, alongside sales orders, quotes, and credit memos. An agent can raise an invoice for a customer and record the payment against it using the customer payment endpoints, keeping the documents linked within the same company.

What are the rate limits for the Dynamics 365 Business Central API?

This OpenAPI spec does not state numeric rate limits; Business Central enforces request limits per environment and tenant set by Microsoft. Check the Microsoft Dynamics 365 Business Central API documentation for the current throttling limits before running high-volume syncs.

How do I create an invoice with the Dynamics 365 Business Central API through Jentic?

Install Jentic One, import Business Central from the API Directory, and store your oauth2 credential once. Your agent then searches by intent, for example 'create a sales invoice', and Jentic returns the matching operation with its input schema and the company id it needs. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Dynamics 365 Business Central

Browse all Dynamics APIs

AI ReadinessFoundational (C-)50/100

See full scorecard

Community OpenAPI document · agent-readyFinanceAccountingoauth2324 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read and write Business Central financial and sales records for a company: customers, vendors, items, sales invoices, orders, quotes, journals, and payments, plus financial statements like the balance sheet and aged receivables. Every path is scoped to a company id.

Use for: List all customers in a company, Create a sales invoice for a customer, Get the balance sheet for a company, Post a general journal entry

Not supported: Does not handle payroll runs, warehouse logistics, or CRM marketing campaigns. Use for Business Central financial, sales, and master-data records within a company only.

The Dynamics 365 Business Central API exposes the standard financial and sales records of a Business Central company over REST. It reads and writes customers, vendors, items, sales invoices, sales orders, quotes, and credit memos, posts journals and customer payments, and manages dimensions, currencies, payment terms, and tax groups. It also returns financial statements such as the balance sheet, cash flow statement, and aged accounts receivable and payable, so an application can run accounting and order-to-cash workflows without the Business Central client.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

64%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

66%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dynamics 365 Business Central to your agent

Capabilities

Start building with Dynamics 365 Business Central API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dynamics 365 Business Central

Jentic AI Readiness Score

(v1.0) Dynamics 365 Business Central

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness