VantegrateNative API integrationIntegrate SAP Business One with AI agentsand talk to your ERP data in plain English
Metrix connects to your ERP through the SAP Business One Service Layer (REST/OData), SAP's modern API, and lets your team ask in plain English about sales, collections, inventory and purchasing. It reads the truth in your ERP and makes it conversational. Your data stays in your SAP Business One instance.
How the data flows
What does it mean to integrate SAP Business One with Vantegrate's AI agents?
Integrating SAP Business One with Vantegrate's AI agents means that Metrix connects to your ERP through the Service Layer (SAP's REST/OData API) and lets your team ask in plain English about what's really going on in your business: how much you invoiced, which customer owes you money, which item's sales dropped or how much stock is left. Metrix reads your entities and answers with the figure and its breakdown.
That is different from a static dashboard someone updates by hand. Here the agent queries the current data in your instance, the same source your finance and operations teams use, and makes it conversational and available in dashboards. For this use case the connection is read-only: Metrix queries and analyzes, and it doesn't change your records. Your business information stays in your SAP Business One.
What do you want to connect to your SAP Business One?
Pick what you need and we'll write the message for you.
1 · Pick what to solve
2 · What our team receives
Vantegrate
online
What data Metrix reads from your SAP Business One
Metrix queries the Service Layer's standard entities in real time, using OData syntax ($filter, $orderby, $top), to answer any question about the operations recorded in your ERP.
Sales and invoicing
Metrix reads Invoices (A/R), Orders and Quotations, cross-referenced with BusinessPartners and Items, to answer how much you invoiced, who your best customers are or which product's sales dropped.
Collections and finance
It combines Invoices, CreditNotes and BusinessPartners to build each customer's account statement and an accounts receivable aging you can ask questions about, without waiting for the month-end report.
Inventory and purchasing
It reads Items, Warehouses, PurchaseOrders and PurchaseInvoices to flag stockouts by warehouse and answer how much you bought from each vendor.
How the integration works, step by step
Vantegrate handles the setup and rollout. Your team authorizes, validates and starts asking.
Connection over the Service Layer
We connect to the SAP Business One Service Layer (REST/OData v4), SAP's modern API, against your instance on SQL Server or SAP HANA. No scrapers and no fragile bridges.
User, session and permissions
We set up authentication (Basic Auth with a reusable session cookie, or OAuth 2.0 with your IdP) and an integration user with the minimum read permissions the use case needs.
Entity mapping
We map the entities Metrix queries (Invoices, Orders, BusinessPartners, Items, Warehouses) and build the OData queries for your most frequent questions.
Validation with real data
We test with your instance and your real data, validate the numbers with your finance and IT teams, and roll out in phases.
The Service Layer vs. a static report
SAP Business One exposes two official APIs: the Service Layer (REST/OData, the modern and recommended one, native to deployments on SAP HANA) and the DI API (COM on Windows, older and lower-level). Both share most of their business object metadata, but the Service Layer adds the REST/OData layer on top. Metrix works with the Service Layer, which is the recommended path for a new integration.
The difference from a static report shows up day to day. Instead of waiting for someone to put together a spreadsheet, your team asks in natural language and Metrix queries the current data with an OData query on the spot. The Service Layer exposes more than 480 entities, so the same connection answers questions about sales, collections, inventory or purchasing without building a different dashboard for each question.
| Dimension | Static report | Metrix on the Service Layer |
|---|---|---|
| Data access | Spreadsheet built by hand | Service Layer (REST/OData), live |
| Freshness | Waits for the next export | Current data from your instance, instantly |
| Scope | One dashboard per question | 480+ entities, a single connection |
| How you ask | Filters and pivot tables | Natural language, in plain English |
| Permissions | Whoever has the file | Read-only integration user |
Comparison of data access patterns; the exact scope is defined with your team based on your instance, your database (SQL Server or HANA) and your entities.
Your data stays in your instance: Metrix queries your SAP Business One through the API and makes it conversational; it doesn't take your database anywhere else. The connection uses a read-only integration user, and every query is logged. The session reuses the B1SESSION cookie and re-authenticates only when it expires.
How it authenticates and keeps the session alive
The Service Layer supports two authentication schemes. The classic one is Basic Authentication: a POST to /Login with the company database, the user name and the password returns a B1SESSION session cookie that travels with every request. Best practice, which Vantegrate follows, is to cache that session and re-authenticate only when it expires, never on every request, so the server isn't overloaded.
Since version 10.0 FP 2305, the Service Layer also supports OAuth 2.0 / OpenID Connect against an identity provider (IdP), designed for SSO and multi-tenant scenarios. The scheme is chosen based on your SAP Business One version and your security policy; in either case, the connection is limited to an integration user with read permissions.
About SAP Business One versions: the OData v3 protocol has been deprecated since FP 2405 (OData v4 is used instead), and OAuth requires at least 10.0 FP 2305 with an IdP configured. The integration adapts to your version and your database, whether it's Microsoft SQL Server or SAP HANA.
You've seen how it connects. Want to walk through your case?
Tell us how your SAP Business One is set up and we'll tell you what data we need and where the agent connects.
An agent connected to your SAP Business One vs. a standalone tool
| Standalone AI tool | Agent connected to your SAP Business One | |
|---|---|---|
| Data source | A copy that drifts | Your source of truth, live |
| Where your data lives | In a third-party system | In your environment, encrypted end to end |
| Result of each operation | Stuck in another app | Written back to your SAP Business One |
| Permissions and audit | Broad and hard to audit | Least-privilege scope and an audit trail |
| Reaching production | Often stalls as a pilot | Validated, phased rollout |
Why make your ERP data conversational
Third-party figures, each with its published source, to size the opportunity. None of them is a Vantegrate result.
480+
Entities the SAP Business One Service Layer exposes for queries, according to SAP
Source: SAP, Service Layer API Reference
95%
Of generative AI pilots never reach production with measurable business impact
The entity count comes from SAP's documentation, not from Vantegrate, and it depends on your version. The MIT NANDA figure reflects the gap between experimenting with AI agents and running them in production.
Which agents run on your SAP Business One
This integration focuses on talking to your ERP data with Metrix; on the same connection, Sellium can add customer service on WhatsApp.
Metrix
Data agent: your team asks in plain English about sales, collections, inventory or purchasing and gets the answer from your ERP's real data, with no static reports and no waiting on IT.
Explore Metrix
Sellium
Sales agent on WhatsApp: with your SAP Business One data at hand (prices, inventory, account balances), it handles and answers sales inquiries in the channel where the customer writes.
Explore SelliumThe integration doesn't take your data anywhere
The principle is simple: AI comes to your data, not your data to the AI. Metrix queries your SAP Business One through the Service Layer, with a read-only integration user, and the agents run on certified cloud infrastructure.
- Connection through the official Service Layer (REST/OData v4) of SAP Business One, with no scrapers and no fragile bridges.
- Metrix queries and analyzes your sales, collections, inventory and purchasing; your database stays in your SAP Business One instance.
- Access scoped by a read-only integration user and minimum permissions, with every query logged.
- The agents run on Salesforce or Oracle Cloud Infrastructure, whose SOC 2 and ISO 27001 certifications belong to those platforms, not to Vantegrate or SAP.
Frequently asked questions about the SAP Business One integration
What finance and IT teams usually ask before connecting an AI agent to their ERP.
How do I integrate SAP Business One with an AI agent?
How do I integrate SAP Business One with an AI agent?
With a connection through the SAP Business One Service Layer (REST/OData v4), SAP's modern API. Metrix reads your entities (Invoices, Orders, BusinessPartners, Items) and your team asks in plain English about sales, collections or inventory. Vantegrate handles the setup and rollout; your team authorizes the integration user, validates the numbers and starts asking. Meet Metrix, the data agent.
Does Vantegrate connect through the Service Layer or the DI API?
Does Vantegrate connect through the Service Layer or the DI API?
Through the Service Layer (REST/OData v4), the modern API of SAP Business One, recommended for cloud and web integrations. The classic DI API is COM on Windows, lower-level, and works with the same business objects; for this data query use case, the Service Layer is the right path. It's best to use OData v4, because v3 has been deprecated since FP 2405.
Does it work with SAP Business One on SQL Server or on HANA?
Does it work with SAP Business One on SQL Server or on HANA?
With both. The Service Layer is the native API of deployments on SAP HANA, and it also runs on the SQL Server version, on-premises or in the cloud. The integration adapts to your database without changing the way your team asks its questions.
How does the connection authenticate, and what data does the agent touch?
How does the connection authenticate, and what data does the agent touch?
Through Basic Authentication (company database, user name and password, with a B1SESSION session cookie that gets reused) or, since 10.0 FP 2305, through OAuth 2.0 / OpenID Connect with your identity provider. The integration user is read-only: Metrix queries and analyzes your data, and it doesn't change your records.
Metrix, the data agent
How your team asks in plain English and gets answers from your ERP's real data.
Learn moreAll integrations
The full map: the ERPs, CRMs and tools the AI agents connect to.
Learn moreAI agents for enterprises
The map of the Vantegrate suite: sales, marketing, documents, data and logistics.
Learn moreLet's connect AI agents to your SAP Business One
Tell us how your instance is set up and we'll show you what Metrix queries, which integration user we request and how the conversation with your sales, collections and inventory data works. A 30-minute conversation, no commitment.
Francisco Morales, co-founder, takes your call. We reply on WhatsApp within 4 business hours, no strings attached.
