canonical: https://jentic.com/apis/swaggerhub.wikigioco/backoffice-crm

# Wikigioco Backoffice CRM

This API manages data about backoffice integration. The API exposes 16 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically dashboard info, dashboard info. Covers 16 operations with apiKey, bearer authentication.

## Scope

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

## Capabilities

- Dashboard Info
- Manage crm data programmatically
- Integrate Backoffice CRM into automated workflows
- Query and filter Backoffice CRM records by parameters
- Monitor Backoffice CRM operational status and events

## Use cases

### CRM Operations

Use the Backoffice CRM to perform crm operations programmatically. The API provides 16 endpoints covering core functionality including dashboard info, dashboard info, dashboard info.

Example prompt: Call POST /crm/catalog/list to dashboard info

### Automated auth Management

Automate auth operations by combining multiple Backoffice CRM endpoints. Agents can dashboard info and then dashboard info in a single workflow.

Example prompt: Call POST /crm/catalog/createProduct to dashboard info, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Backoffice CRM 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 apiKey, bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /crm/catalog/list | Dashboard Info |
| POST | /crm/catalog/createProduct | Dashboard Info |
| POST | /crm/catalog/createCatalog | Dashboard Info |
| POST | /crm/catalog/status | Dashboard Info |
| POST | /crm/catalog/config | Dashboard Info |
| POST | /crm/catalog/getOne | Dashboard Info |
| POST | /report/dashboard | Dashboard Info |
| POST | /network/mgt/updateMerchant | Create or Modify Vmerchantlist |

## Key resources

- **auth** — All services provided for User mgt and Authentication
- **bo** — All the services provided by Gams backoffice
- **get** — All the services to get an object
- **create** — All the services to create an object
- **update** — All the services to modify an object

## Why Jentic

- **Setup:** Wiring Backoffice CRM by hand means choosing among its auth options (a bearer token, an X-API-Key header, or an api_key query parameter), attaching the chosen credential to every catalog, report, and network call, and managing it yourself. Through Jentic you install once, import Backoffice CRM from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Backoffice CRM sends its catalog and merchant targets in the request body rather than the URL path, so scope with operations-only language: limit the agent to the operations it needs, such as listing the catalog or reading the dashboard. You choose the operations it may call, so state-changing ones like creating a product or updating a merchant are not included unless you add them.
- **Credential handling:** Your Backoffice CRM credential 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 'list the product catalog' or 'get dashboard reporting', and Jentic returns the matching Backoffice CRM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Backoffice CRM use?

The Backoffice CRM uses apiKey, bearer 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 dashboard info with the Backoffice CRM?

Yes. Use the POST /crm/catalog/list endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Backoffice CRM?

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 dashboard info through Jentic?

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

### How many endpoints does the Backoffice CRM have?

The Backoffice CRM exposes 16 endpoints covering auth, bo, get operations.

### Can I limit what my agent is allowed to do with the Backoffice CRM API?

Yes. Because you run Jentic One yourself, you decide which Backoffice CRM operations your agent may call, and your own rules are what grant access. You can restrict it to read-only operations such as listing the product catalog (POST /crm/catalog/list) or reading the dashboard report (POST /report/dashboard), while state-changing operations like creating a product (POST /crm/catalog/createProduct) or updating a merchant (POST /network/mgt/updateMerchant) stay off unless you add them. The stored credential is injected only when the agent runs an operation you have allowed, so it never sees the raw secret.