> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/integration/bevica_website_integration.md).

# Bevica Website Integration

Sync customers, items, prices, and orders between Bevica and your website.

The Bevica Web Integration extension lets you connect your e‑commerce website directly with Bevica.

In practice, this means Bevica can publish item, pricing, and stock information to your website, while incoming web orders flow back into Bevica for processing and distribution.

This guide is designed for Bevica users who will configure and maintain the integration, as well as those responsible for reviewing and managing web orders.

<a class="button primary" data-icon="microsoft">Requires Bevica Essentials extension to be installed</a>

{% hint style="info" %}
Bevica Web Integration is a separate extension. Please contact your system administrator or your TVT contact if you would like further information or would like to install Bevica Web Integration.
{% endhint %}

The **Bevica Web Integration** extension makes available a number of endpoints. These are published as API (V2.0), learn more

* Microsoft documentation: [Welcome to the API (v2.0) for Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/).
* Bevica technical documentation: [API Reference](https://kb.bevica.com/api-reference/readme.md)

### Data available

#### Bevica outbound

* Customer Ledger Entries
* Customer
* Item
* Manifest Lines
* Manifest
* Marketing Content
* Order Status
* Paid Reserve Entries
* Paid Reserve
* Posted Sales Credit Memo Header
* Posted Sales Credit Memo Line
* Posted Sales Invoice Header
* Posted Sales Invoice Line
* Sales Price List Prices
* Sales Prices
* Ship-to Address
* Stock
* Web Product

#### Bevica inbound

* Payments
* Web Orders: header and lines


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.bevica.com/documentation/integration/bevica_website_integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
