canonical: https://jentic.com/apis/swaggerhub.wwg-integration/wwg-integration-b2b

# WWG Integration B2B

SAP interface for B2B Integration. The API exposes 23 endpoints.

## For AI agents

Programmatically authentication token, add/update product styles. Covers 23 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Authentication token
- Add/Update product styles
- Integrate WWG Integration B2B into automated workflows
- Query and filter WWG Integration B2B records by parameters
- Monitor WWG Integration B2B operational status and events

## Use cases

### Developer Tools Operations

Use the WWG Integration B2B to perform developer tools operations programmatically. The API provides 23 endpoints covering core functionality including authentication token, add/update product styles, add/update customer bill-to records.

Example prompt: Call POST `/authorizationserver/oauth/token` to authentication token

### Automated Accountreceivable Management

Automate accountreceivable operations by combining multiple WWG Integration B2B endpoints. Agents can add/update product styles and then add/update customer bill-to records in a single workflow.

Example prompt: Call PUT `/products/styles` to add/update product styles, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WWG Integration B2B endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'authentication token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/authorizationserver/oauth/token` | Authentication token |
| PUT | `/products/styles` | Add/Update product styles |
| PUT | `/customers/billTo` | Add/Update customer bill-to records |
| PUT | `/customers/soldTo` | Add/Update customer sold-to records |
| PUT | `/customers/shipTo` | Add/Update customer ship-to records |
| PUT | `/customers/catalog` | Add/Update customer catalogue records |
| PUT | `/priceRowsBatch` | Add/Update a customer price record |
| PUT | `/discountRows` | Add/Update a customer price discount record |

## Key resources

- **Accountreceivable** — Operations for accountReceivable
- **Authorizationserver** — Operations for authorizationserver
- **Availableinventory** — Operations for availableInventory
- **Customers** — Operations for customers
- **Discountrows** — Operations for discountRows

## Why Jentic

- **Setup:** Wiring WWG Integration B2B by hand means driving its OAuth token endpoint, then coding each customer, product, and price PUT against its host with the right payload shape yourself. Through Jentic you install once, import WWG Integration B2B from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This B2B integration carries its targets in the request body across the customer, product, and price endpoints, so limit the agent to the operations it needs, such as updating product styles or a price rows batch. You decide which feeds it may write, and the rest stay out of reach.
- **Credential handling:** Any credential you configure for WWG Integration B2B 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.
- **Discovery method:** Agents search Jentic by intent such as 'update product styles' or 'push a price rows batch', and Jentic returns the matching WWG Integration B2B operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the WWG Integration B2B use?

The WWG Integration B2B uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I authentication token with the WWG Integration B2B?

Yes. Use the POST `/authorizationserver/oauth/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WWG Integration B2B?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I authentication token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authentication token'. Jentic returns the matching WWG Integration B2B operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WWG Integration B2B have?

The WWG Integration B2B exposes 23 endpoints covering accountreceivable, authorizationserver, availableinventory operations.

### Can I limit what my agent is allowed to do with the WWG Integration B2B API?

Yes. Because Jentic One is self-hosted and its access rules are yours to set, you decide which WWG Integration B2B operations the agent may call. Since this integration carries its targets in the request body across the customer, product, and price endpoints, you can grant only the writes you intend, such as PUT `/products/styles` or PUT /priceRowsBatch, while leaving customer bill-to, sold-to, and ship-to updates out of reach. The credential you configure is held by your own instance and injected only for the operations you permit.