Wikigioco Auth Generated Service
Browse all Swaggerhub Wikigioco APIs★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey, bearer46 EndpointsREST
For Agents
Programmatically list of app filter by pagination, list of app filter by queryparam. Covers 46 operations with apiKey, bearer authentication.
Use for: I need to of app filter by pagination, I want to of app filter by queryparam, Search for or modify app, Find all one of app filter by parameter id
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
This API manages Auth auto-generated for backoffice management. The API exposes 46 endpoints secured with apiKey, bearer authentication.
Install Jentic One Beta
Connect the Auth Generated Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Auth Generated Service, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.wikigioco%2Fauth-generated-service" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.wikigioco%2Fauth-generated-service" | 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 Auth Generated Service API.
List of app filter by Pagination
Create or Modify App
get one of app filter by parameter Id
Query and filter Auth Generated Service records by parameters
Monitor Auth Generated Service operational status and events
Use Cases
Patterns agents use Auth Generated Service API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Auth Generated Service to perform identity auth operations programmatically. The API provides 46 endpoints covering core functionality including list of app filter by pagination, list of app filter by queryparam, create or modify app.
Call POST /app/pagination to list of app filter by pagination
Automated app Management
Automate app operations by combining multiple Auth Generated Service endpoints. Agents can list of app filter by queryparam and then create or modify app in a single workflow.
Call GET /app/list to list of app filter by queryparam, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Auth Generated Service 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 'list of app filter by pagination', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
46 endpoints — this api manages auth auto-generated for backoffice management.
METHOD
PATH
DESCRIPTION
POST
/app/pagination
List of app filter by Pagination
GET
/app/list
List of app filter by queryParam
POST
/app/
Create or Modify App
GET
/app/{appName}
get one of app filter by parameter Id
POST
/attachmentcommunication/pagination
List of attachmentcommunication filter by Pagination
GET
/attachmentcommunication/list
List of attachmentcommunication filter by queryParam
POST
/attachmentcommunication/
Create or Modify Attachmentcommunication
GET
/attachmentcommunication/{communicationId}/{documentId}
get one of attachmentcommunication filter by parameter Id
POST
/app/pagination
List of app filter by Pagination
GET
/app/list
List of app filter by queryParam
POST
/app/
Create or Modify App
GET
/app/{appName}
get one of app filter by parameter Id
POST
/attachmentcommunication/pagination
List of attachmentcommunication filter by Pagination
GET
/attachmentcommunication/list
List of attachmentcommunication filter by queryParam
POST
/attachmentcommunication/
Create or Modify Attachmentcommunication
GET
/attachmentcommunication/{communicationId}/{documentId}
get one of attachmentcommunication filter by parameter Id
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Auth Generated Service by hand means supporting both its bearer JWT and its X-API-Key schemes, picking the right host between the virtserver mock and the test.wikigioco.com backoffice, and threading identity calls yourself. Through Jentic you install once, import the Auth Generated Service from the API Directory, store the credential once, and your agent calls it.
Permission scoping
This service puts the app name in the URL path (/app/{appName}/...), so a rule can pin your agent to one app: it can read and manage that app and nothing else. You choose the operations it may call, so writes like creating an app or an attachment communication are not included unless you add them.
Credential isolation
Your Auth Generated Service bearer token or API key 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.
Intent-based discovery
Agents search Jentic by intent such as 'list apps by pagination' or 'fetch an app by name', and Jentic returns the matching Auth Generated Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Auth Generated Service API through Jentic.
What authentication does the Auth Generated Service use?
The Auth Generated Service 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 list of app filter by pagination with the Auth Generated Service?
Yes. Use the POST /app/pagination endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Auth Generated Service?
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 list of app filter by pagination through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list of app filter by pagination'. Jentic returns the matching Auth Generated Service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Auth Generated Service have?
The Auth Generated Service exposes 46 endpoints covering app, attachmentcommunication, comunication operations.
Can I limit what my agent is allowed to do with the Auth Service API?
Yes. Because you run Jentic One yourself, your own rules decide which Auth Service operations and credentials the agent may use. Since the app name sits in the URL path (/app/{appName}/...), you can pin the agent to a single app so it reads and manages that one app and nothing else. You also pick the exact operations it may call, so write actions such as creating or modifying an app or an attachment communication stay off limits unless you add them.
GET STARTED