Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Qigu Open API Documentation
Qigu Open API Documentation logo

Qigu App Qigu Open API Documentation

61
AI ReadinessAI-Aware (B-)61/100
See full scorecard
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer15 EndpointsREST

For Agents

Programmatically returns the list of the countries, returns the list of the languages. Covers 15 operations with bearer authentication.

Use for: I need to returns the list of the countries, I want to returns the list of the languages, Search for creates a new client, Find all returns the list of your clients

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

This document describes the differents endpoints you can use with the **Company Authentification Token** (provided by Qigu Admin).<br/>If you provide a **webhook url** in Qigu Admin, our API will call yours when specific events happens. The API exposes 15 endpoints secured with bearer authentication.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Qigu Open API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Qigu Open API Documentation, 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%2Fqigu.app%2Fqigu" | sh
2

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%2Fqigu.app%2Fqigu" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Qigu Open API Documentation API.

Returns the list of the countries

Creates a new client

Updates an existing client

Access Qigu Open API Documentation developer tools resources via REST API

Use Cases

Patterns agents use Qigu Open API Documentation API for, with concrete tasks.

★ Developer Tools Operations

Use the Qigu Open API Documentation to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including returns the list of the countries, returns the list of the languages, creates a new client.

Call GET /countries to returns the list of the countries

Automated countries Management

Automate countries operations by combining multiple Qigu Open API Documentation endpoints. Agents can returns the list of the languages and then creates a new client in a single workflow.

Call GET /languages to returns the list of the languages, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Qigu Open API Documentation 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 bearer tokens manually.

Search Jentic for 'returns the list of the countries', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — this document describes the differents endpoints you can use with the **company authentification token** (provided by qigu admin).

METHOD

PATH

DESCRIPTION

GET

/countries

Returns the list of the countries

GET

/languages

Returns the list of the languages

POST

/companies

Creates a new client

GET

/companies

Returns the list of your clients

PUT

/companies/{id}

Updates an existing client

GET

/programs

Returns the list of your programs

POST

/journeys

Creates a new journey

GET

/journeys

Returns the list of your distributions

GET

/countries

Returns the list of the countries

GET

/languages

Returns the list of the languages

POST

/companies

Creates a new client

GET

/companies

Returns the list of your clients

PUT

/companies/{id}

Updates an existing client

GET

/programs

Returns the list of your programs

POST

/journeys

Creates a new journey

GET

/journeys

Returns the list of your distributions

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

Q

Qigu Open API Documentation

- AI-Aware (B-)
61/100
55
Foundational Compliance
63
Developer Experience & Jentic Compatibility
50
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
56
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
55

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4
92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
26%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

50

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4
46%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

56

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1
56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Qigu API by hand means setting up its bearer auth and handling company, program, and journey calls yourself. Through Jentic you install once, import the Qigu API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Qigu puts the company id in the URL path (/companies/{id}), so a rule can pin your agent to one company: it can update that company and nothing else. You choose the operations it may call, so creating journeys is not included unless you add it.

Credential isolation

Your Qigu token 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 supported countries' or 'create a journey', and Jentic returns the matching Qigu 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.

Alternative

Github

→

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Qigu Open API Documentation API through Jentic.

What authentication does the Qigu Open API Documentation use?

The Qigu Open API Documentation uses a Bearer token in the Authorization header. 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 returns the list of the countries with the Qigu Open API Documentation?

Yes. Use the GET /countries endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Qigu Open API Documentation?

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 returns the list of the countries through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns the list of the countries'. Jentic returns the matching Qigu Open API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Qigu Open API Documentation have?

The Qigu Open API Documentation exposes 15 endpoints covering countries, companies, files operations.

Can I limit what my agent is allowed to do with the Qigu API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which Qigu operations and credentials your agent may use. Since Qigu puts the company id in the URL path, such as PUT /companies/{id}, you can pin the agent to a single company so it updates that record and nothing else. You also pick the exact operations it may call, so creating journeys with POST /journeys stays off unless you explicitly allow it.

GET STARTED

Start building with Qigu Open API Documentation API

Explore with Jentic One
View OpenAPI Document