Developers DevOps SaaS teams schedule 6 min

Integrate Konso into your systems

Use the Konso Public API to automate content, observability, and platform workflows.

What is Konso Public API

The Konso Public API provides programmatic access to core platform capabilities including observability, headless CMS, AI-powered content generation, agents, and integrations. All endpoints are secured and exposed via versioned REST and gRPC interfaces.

  • check_circle Automate content generation and delivery
  • check_circle Integrate observability data into internal tools
  • check_circle Embed Konso into CI/CD pipelines
  • check_circle Build custom workflows and SaaS integrations

What you can do

  • Manage projects and environments
  • Create and update structured content
  • Fetch logs, metrics, and business events
  • Trigger automated agents
  • Integrate with external systems

Who is it for

  • Backend and platform engineers
  • DevOps and automation workflows
  • SaaS integrations and internal tooling
  • AI-driven content pipelines

Authentication

Konso uses API key–based authentication. Every request must include the x-api-key header with your personal API key.

REST Authentication http
x-api-key: <YOUR_API_KEY>
REST Example http
GET /v1/cms/pages/{projectId}
Host: apis-spb.konso.io
x-api-key: <YOUR_API_KEY>
gRPC Metadata bash
x-api-key: <YOUR_API_KEY>
warning

Keep your API key secret. Do not expose it in client-side code or public repositories.

Request / Response Format

All Konso API endpoints use JSON over HTTPS and follow a consistent response structure.

Common Headers http
Accept: application/json
Content-Type: application/json

POST Endpoints

POST endpoints are used to create new entities. Each request uses a dedicated request model with validation.

Response Model json
{
  "result": true,
  "validationErrors": [],
  "errors": []
}

Status Codes

  • 201 Created — success
  • 400 Bad Request — validation errors returned in validationErrors
  • 500 Internal Server Error — runtime errors returned in errors

Рекомендации

  • verified Store API keys in secure vaults or environment variables
  • verified Avoid exposing API calls from frontend applications
  • verified Use pagination for large datasets
  • verified Implement retry logic for transient failures

Оставаясь на сайте, Вы даете свое согласие на использование файлов cookie