Connect EBP Gestion Commerciale to Persyst

Persyst lets you query EBP Gestion Commerciale SaaS from an MCP-compatible assistant. An administrator connects a folder with an EBP application, then opens the source and the required tools to selected people or teams.

The connector is read-only. It covers items, customer and supplier identity, inventory, sales and purchase documents and selected reference data. See the EBP connector overview.

Prepare EBP accessCopy section link

Check with EBP that your subscription includes the Gestion Commerciale SaaS API. The EBP help center states that a support contract is required for the REST API module. EBP licensing and terms still apply.

Prepare four values using the EBP developer portal and your application owner:

Have EBP authorize your application’s redirect URL. For the standard hosted Persyst service:

https://api.persyst.ai/integrations/ebp/callback

The EBP authentication documentation explains how to have this URL authorized. For another Persyst deployment, use that deployment’s API address followed by /integrations/ebp/callback; locally, configure it with EBP_CALLBACK_URL. EBP must also accept a local URL before you can test consent.

OAuth authorization requests openid profile offline_access. It requires interactive consent: application credentials alone do not replace authorization by an account with folder access.

Find the folder IDCopy section link

From the portal or an authorized API client, use Obtenir les dossiers de gestion (list management folders):

GET https://api-developpeurs.ebp.com/gescom/api/v1/Folders

Find the matching name and its id in folders, reading subsequent pages when necessary. This native EBP ID differs from the sourceId Persyst will assign to the connection. Assistants do not need the OAuth token or subscription key.

Connect the folder in PersystCopy section link

1. In Data sources → Add a source, choose EBP.
2. Enter the four prepared values in the Persyst form.
3. Click Authorize in EBP and authorize the EBP account that can read the selected folder.
4. On return, check EBP · folder name. Persyst verifies the folder through the API before activating the connection.
5. In Access management, grant the source and select tools for the intended users.

Create one source per folder to separate access. Members read with the shared connection and their granted Persyst permissions, not with their own EBP identity. The account that authorized the connection limits what the API can return.

Secrets are encrypted on the server. Enter them in the form, never in a conversation with your assistant.

Select authorized toolsCopy section link

The ebp_api catalog does not grant access to all data on its own. For example, reading inventory through it also requires read_ebp_stock. Permissions are checked for every call; withdrawing access blocks subsequent reads. Calls appear in Persyst usage tracking.

Query the API catalog from the assistantCopy section link

Recommended technical flow:

1. Call list_ebp_folders and keep the Persyst sourceId for the intended source.
2. Call ebp_api with action: "search" and a query such as stock.
3. Use action: "describe" with the returned operation for its parameters, then action: "fields" for known columns.
4. Read using the business tool or action: "read", selecting required columns and a validated filter.
5. When nextOffset is present, read the next page. Do not present a partial page as an exhaustive total.

The eleven operations are items, customers, suppliers, stock, sales, purchases, families, subfamilies, groups, storehouses and supplier_items. Example inventory read after identifying the source:

{
  "sourceId": "<Persyst sourceId>",
  "action": "read",
  "operation": "stock",
  "parameters": {
    "columns": ["ItemId", "StorehouseId", "RealStock", "VirtualStock"],
    "limit": 25,
    "offset": 0
  }
}

Read results include results, total, offset, returned, nextOffset, partial and retrievedAt. Sales and purchases accept documentType, toDate, durationDays (30 by default) and withLines. Use EBP’s documented document types without guessing their meaning.

Fields and limitsCopy section link

The catalog exposes a known subset of columns with schemaComplete: false, not an exhaustive EBP schema export. EBP documents exporting the schema from its application. That export is a reference for extending the connector, not a URL assistants can call freely.

• One page per call: 25 rows by default, at most 100, with a maximum offset of 100,000.
• API responses are limited to 2 MiB and each request to 15 seconds. Reduce selected columns or page size if needed.
• Only supported tables, columns, routes and filters are accepted. Assistants cannot supply arbitrary URLs, SQL or YAML.
• No writes, PDFs, forecasting, accounting, HUBBIX or Bâtiment access in this version.

Check and maintain the connectionCopy section link

Test a known reference with an authorized member: ask for an item’s inventory or documents over a short period. Also check that a member without access cannot see the source. Connect your assistant covers setup on the AI side.

If EBP refuses authorization or token refresh cannot complete, Persyst requests a reconnection. Open Source connection → Reconnect: the source keeps its folder and access settings. EBP refresh tokens rotate; do not reuse tokens managed by Persyst in another script. A connection left unused for a long period may require fresh consent.

If the subscription key or application credentials change, prepare a new connection with the new values, reassign access, then remove the old source.

Reference: EBP Gestion Commerciale API and authentication.