Connect your customers' Business Central tenants so your product can read and write items, customers, vendors, and transactions without managing Microsoft OAuth flows yourself. The customer's admin consents on Microsoft's screen; Askel stores the aadTenantId and environment name and handles token refresh.
Fetch Business Central customer cards with name, address, payment terms, and credit limit, or create new customers that your product's onboarding flow discovers. Covers both domestic and foreign customer groups.
Read the item catalog including unit price, unit of measure, inventory quantity, and item type. Create or update items when your product's catalog changes need to propagate to Business Central.
Create sales orders or posted sales invoices in the customer's Business Central company, with line items, quantity, price, and general ledger account references.
Fetch vendor records and open purchase orders so your product can surface procurement status or sync purchase confirmations back to Business Central.
Pull G/L account lists and posted G/L entries for financial reporting or reconciliation workflows that need to show actual ledger state from Business Central.
Fetch the list of companies within the customer's Business Central environment so your product can scope writes to the correct company when the tenant has multiple companies configured.
You sell a field-sales enablement platform. A new customer, Harwick Distributors, uses Business Central to manage inventory and fulfil orders. When a sales rep closes a deal in your platform, Harwick wants a sales order created in Business Central automatically, without waiting for someone to re-enter it.
Harwick's IT admin clicks Connect Business Central in your product. Askel redirects to Microsoft's consent screen. The admin approves, and Microsoft returns an OAuth token. Askel also reads the aadTenantId and stores it alongside the environment name Harwick provides (Production).
Askel calls the Business Central OData metadata endpoint to list all companies in the Production environment. Harwick has two companies: Harwick Distributors Ltd and Harwick Ireland. The admin selects Harwick Distributors Ltd as the target.
Askel reads the item catalog from Business Central. Your platform's admin maps each product SKU in your system to the matching Business Central item number. Unmatched items are flagged for manual mapping.
When a sales rep marks a deal as won in your platform, your product calls Askel to POST a sales order to Harwick's Business Central company. The order includes the customer reference, line items with item numbers and quantities, and the ship-to address from the deal record.
Askel reads the posted sales order number from Business Central and stores it against the deal record in your platform. Harwick's order desk sees the order in Business Central immediately and can start fulfilment.
The customer's Microsoft admin consents on the standard Microsoft identity platform screen. Askel stores the refresh token, the aadTenantId (read from the token claims), and the Business Central environment name supplied by the customer. Every API request is scoped to https://api.businesscentral.dynamics.com/<aadTenantId>/<environment>/api/v2.0/. Access tokens are minted per request and expire after one hour.
© 2025 Askel.ai. All rights reserved.