Wikigioco Backoffice CRM
Browse all Swaggerhub Wikigioco APIs★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey, bearer16 EndpointsREST
For Agents
Programmatically dashboard info, dashboard info. Covers 16 operations with apiKey, bearer authentication.
Use for: I need to dashboard info, I want to dashboard info, Search for dashboard info, Find all dashboard info
Not supported: Does not handle payments, communications, or developer tools — use for crm only.
This API manages data about backoffice integration. The API exposes 16 endpoints secured with apiKey, bearer authentication.
Install Jentic One Beta
Connect the Backoffice CRM to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Backoffice CRM, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Backoffice CRM API.
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
Patterns agents use Backoffice CRM API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'dashboard info', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
16 endpoints — this api manages data about backoffice integration.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Backoffice CRM apiKey, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'dashboard info') and Jentic returns the matching Backoffice CRM operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Backoffice CRM integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Backoffice CRM API through Jentic.
What authentication does the Backoffice CRM use?
The Backoffice CRM uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED