Kibi API

The Kibi REST API allows external applications, AI assistants, and automations to access Kibi Connect data. The API can read and write content—from wiki pages to news posts, tasks, and calendar entries.

Enable API Access#

The REST API must first be enabled by a system administrator. The setting is located under:

Settings → Integrations → REST API

The following options are available:

• Enable REST API

  Turns the API interface on or off.

• Restrict token creation to specific roles

  If enabled, only users with the selected roles can create API tokens. Individual users can additionally be authorized via the function access in the Security tab of their profile.

• Enable IP restriction

  If enabled, only the specified IP addresses can access the API. This is an additional security layer.

Create API Token#

Each user can create their own API tokens via their user profile. To do this, navigate to:

User Profile → Integrations → Create New Token

When creating a token, you assign:

• Name

  A descriptive name (e.g., "AI Agent", "ERP Integration", "Workflow Automation").

• Permissions (Scopes)

  Select only the permissions that the integration actually needs (principle of least privilege).

• Expiration date (optional)

  Optionally, an expiration date can be set after which the token automatically becomes invalid.

Securely Store Token#

After creation, the token value is displayed only once. Copy it immediately and store it securely (e.g., in a password manager). If lost, the token must be revoked and a new one created.

Available Permissions (Scopes)#

The following scopes control the API token's access to different areas:

API Authentication#

All API requests must include the token as a Bearer token in the Authorization header:

curl -H "Authorization: Bearer kbc_YourTokenHere" \
     https://your-company.kibi.de/api/v1/wiki

The API base URL is: https://your-company.kibi.de/api/v1

Available Endpoints#

The complete API documentation with all endpoints and parameters is available directly in Kibi Connect under:

• Interactive Documentation: User Profile → Integrations → API Documentation

• OpenAPI Specification (JSON): User Profile → Integrations → OpenAPI JSON

Key endpoints at a glance:

Automation with n8n#

For workflow automation without writing your own code, there is the official n8n Community Node for Kibi Connect. Setup, trigger operation, and example workflows are described on the page n8n Integration: Automate Kibi Connect.

Manage Tokens#

All created tokens are displayed in the overview under User Profile → Integrations. Here you see:

• The token name

• The assigned permissions

• When the token was last used

• The option to revoke a token

Important Notes#

• Data Access: API tokens only have access to the data that the respective user also has access to. The user's permissions still apply.

• Security: Never share API tokens publicly. Store tokens in environment variables or a secret manager, not in source code.

• Least Privilege: Grant only the minimum necessary permissions. A token for a wiki integration does not need access to chat.

• Expiration Date: For temporary integrations, set an expiration date to increase security.

• Revocation: Immediately revoke no longer needed tokens via the token overview.