コンテンツにスキップ
Kong Logo | Kong Docs Logo
  • ドキュメント
    • API仕様を確認する
      View all API Specs すべてのAPI仕様を表示 View all API Specs arrow image
    • ドキュメンテーション
      API Specs
      Kong Gateway
      軽量、高速、柔軟なクラウドネイティブAPIゲートウェイ
      Kong Konnect
      SaaSのエンドツーエンド接続のための単一プラットフォーム
      Kong AI Gateway
      GenAI インフラストラクチャ向けマルチ LLM AI Gateway
      Kong Mesh
      Kuma と Envoy をベースにしたエンタープライズサービスメッシュ
      decK
      Kongの構成を宣言型で管理する上で役立ちます
      Kong Ingress Controller
      Kubernetesクラスタ内で動作し、Kongをプロキシトラフィックに設定する
      Kong Gateway Operator
      YAMLマニフェストを使用してKubernetes上のKongデプロイメントを管理する
      Insomnia
      コラボレーティブAPI開発プラットフォーム
  • Plugin Hub
    • Plugin Hubを探索する
      View all plugins すべてのプラグインを表示 View all plugins arrow image
    • 機能性 すべて表示 View all arrow image
      すべてのプラグインを表示
      AI's icon
      AI
      マルチ LLM AI Gatewayプラグインを使用してAIトラフィックを管理、保護、制御する
      認証's icon
      認証
      認証レイヤーでサービスを保護する
      セキュリティ's icon
      セキュリティ
      追加のセキュリティレイヤーでサービスを保護する
      トラフィック制御's icon
      トラフィック制御
      インバウンドおよびアウトバウンドAPIトラフィックの管理、スロットル、制限
      サーバーレス's icon
      サーバーレス
      他のプラグインと組み合わせてサーバーレス関数を呼び出します
      分析と監視's icon
      分析と監視
      APIとマイクロサービストラフィックを視覚化、検査、監視
      変革's icon
      変革
      Kongでリクエストとレスポンスをその場で変換
      ログ記録's icon
      ログ記録
      インフラストラクチャに最適なトランスポートを使用して、リクエストと応答データをログに記録します
  • サポート
  • コミュニティ
  • Kongアカデミー
デモを見る 無料トライアルを開始
Kong Konnect
  • Home icon
  • Kong Konnect
  • Getting Started
  • Add your API to Konnect
report-issue問題を報告する
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • ドキュメント投稿ガイドライン
  • Introduction
    • Overview of Konnect
    • Architecture
    • Network Resiliency and Availability
    • Port and Network Requirements
    • Private Connections to Other Cloud Providers
      • Create a private connection with AWS PrivateLink
    • Geographic Regions
    • Centralized consumer management
    • Compatibility
    • Stages of Software Availability
    • Release Notes
    • Support
      • Control Plane Upgrades FAQ
      • Supported Installation Options
  • Get Started
    • Overview
    • Add your API
    • Migrating a Self-Managed Kong Gateway into Konnect
  • Gateway Manager
    • Overview
    • Dedicated Cloud Gateways
      • Overview
      • Provision a Dedicated Cloud Gateway
      • Securing Backend Traffic
      • Transit Gateways
      • Azure VNET Peering
      • Custom Domains
      • Custom Plugins
      • Data plane logs
    • Serverless Gateways
      • Overview
      • Provision a serverless Gateway
      • Securing Backend Traffic
      • Custom Domains
    • Data Plane Nodes
      • Installation Options
      • Upgrade a Data Plane Node
      • Verify a Data Plane Node
      • Secure Control Plane/Data Plane Communications
      • Renew Data Plane Certificates
      • Parameter Reference
      • Using Custom DP Labels
    • Control Plane Groups
      • Overview
      • Working with Control Plane Groups
      • Migrate Configuration into Control Plane Groups
      • Conflicts in Control Planes
    • Kong Gateway Configuration in Konnect
      • Overview
      • Manage Plugins
        • Overview
        • Adding Custom Plugins
        • Updating Custom Plugins
        • How to Create Custom Plugins
      • Create Consumer Groups
      • Secrets Management
        • Overview
        • Konnect Config Store
        • Set Up and Use a Vault in Konnect
      • Manage Control Plane Configuration with decK
    • Active Tracing
      • Overview
    • KIC Association
    • Backup and Restore
    • Version Compatibility
    • Troubleshooting
  • Mesh Manager
    • Overview
    • Create a mesh with the Kubernetes demo app
    • Federate a zone control plane to Konnect
    • Migrate a self-managed zone control plane to Konnect
  • Service Catalog
    • Overview
    • Integrations
      • Overview
      • Datadog
      • GitHub
      • GitLab
      • PagerDuty
      • SwaggerHub
      • Traceable
      • Slack
    • Scorecards
  • API Products
    • Overview
    • Product Documentation
    • Productize a Service
  • Dev Portal
    • Overview
    • Dev Portal Configuration Preparation
    • Create a Dev Portal
    • Sign Up for a Dev Portal Account
    • Publish an API to Dev Portal
    • Access and Approval
      • Manage Developer Access
      • Manage Developer Team Access
      • Add Developer Teams from IdPs
      • Manage Application Registrations
      • Configure generic SSO for Dev Portal
      • Configure Okta SSO for Dev Portal
    • Application Lifecycle
    • Register and create an application as a developer
    • Enable and Disable App Registration for API Product Versions
    • Dynamic Client Registration
      • Overview
      • Okta
      • Curity
      • Auth0
      • Azure
      • Custom IdP
    • Portal Management API Automation Guide
    • Audit Logging
      • Overview
      • Set up an Audit Log Webhook
      • Set up an Audit Log Replay Job
    • Portal Customization
      • Overview
      • About Self-Hosted Dev Portal
      • Host your Dev Portal with Netlify
      • Custom Domains
    • Dev Portal SDK
    • Troubleshoot
  • Advanced Analytics
    • Overview
    • Dashboard
    • Explorer
    • Analyze API Usage and Performance with Reports
    • Requests
  • Org Management
    • Plans and Billing
    • Authentication and Authorization
      • Overview
      • Teams
        • Overview
        • Manage Teams
        • Teams Reference
        • Roles Reference
      • Manage Users
      • Manage System Accounts
      • Personal Access Tokens
      • Social Identity Login
      • Org Switcher
      • Configure Generic SSO
      • Configure Okta SSO
      • Login Sessions Reference
      • Troubleshoot
    • Audit Logging
      • Overview
      • Set up an Audit Log Webhook
      • Set up an Audit Log Replay Job
    • Account and Org Deactivation
  • API
    • Overview
    • API Request API (Beta)
      • API Spec
    • API Products API
      • API Spec
    • Audit Logs API
      • API Spec
      • Audit Log Webhooks
    • Control Plane API
      • API Spec
    • Control Plane Configuration API
      • API Spec
    • Cloud Gateways API
      • API Spec
    • Identity API
      • API Spec
      • Identity Integration Guide
      • SSO Customization
    • Konnect Search API (Beta)
      • API Spec
    • Mesh Manager API
      • API Spec
      • Kong Mesh API Reference
    • Portal Client API
      • API Spec
    • Portal Management API
      • API Spec
    • Reference
      • Filtering
      • API Errors
  • Reference
    • Labels
    • Plugin Ordering Reference
    • Konnect Search
    • Terraform Provider
    • Audit Logs
    • Verify audit log signatures
    • IdP SAML attribute mapping
enterprise-switcher-icon 次に切り替える: OSS
On this pageOn this page
  • Prerequisites
  • Add your API
  • Verify the implementation
  • Next steps

このページは、まだ日本語ではご利用いただけません。翻訳中です。

Add your API to Konnect

If you used the in-app onboarding wizard when you logged in to Konnect for the first time, you should already have a demo service.

In this guide, you will build on your Konnect environment by adding your own API to Konnect using services and routes.

What are services and routes?

Services: A service is an entity representing an external upstream API or microservice. For example, a data transformation microservice, a billing API, and so on.

Routes: Routes determine how (and if) requests are sent to their services after they reach the gateway. Where a service represents the backend API, a route defines what is exposed to clients. A single service can have many routes. Once a route is matched, the gateway proxies the request to its associated service.

Prerequisites

  • A Konnect account
  • If you didn’t use the in-app onboarding wizard in Konnect, open the Konnect Gateway Manager, and create a new data plane node.

Add your API

Konnect UI
Konnect API
  1. In the runtimes icon Gateway Manager, select the Default control plane.

  2. Select Gateway Services from the side navigation bar, then New Gateway Service.

  3. From the Add a Gateway Service dialog, create a new service:

    1. Enter a unique name for the Gateway service, or specify a Gateway service that doesn’t yet have a version connected to it.

      For the purpose of this example, enter example_gateway_service.

      The name can be any string containing letters, numbers, or the following characters: ., -, _, ~, or :. Do not use spaces.

      For example, you can use example_service, ExampleService, Example-Service. However, Example Service is invalid.

    2. In the Upstream URL field, enter https://httpbin.konghq.com.

    3. Use the defaults for the remaining fields.

    4. Click Save.

  4. Add a route to your service implementation by clicking the Add a Route button now visible from the Gateway service dashboard.

    For this example, enter the following:

    • Name: httpbin
    • Protocols: HTTP, HTTPS
    • Path(s): /mock
  5. Click Save.

The Konnect API uses Personal Access Token (PAT) authentication. You can obtain your PAT from the personal access token page. The PAT must be passed in the Authorization header of all requests.

  1. Get the list of all control planes so you can copy the control plane ID associated with the default control plane:
      curl --request GET \
     --url https://us.api.konghq.com/v2/control-planes \
     --header 'Authorization: Bearer <personal-access-token>' \
     --header 'accept: application/json'
    

    In this guide, we will assign your service to the default control plane for the sake of simplicity.

  2. Create a service for your API that is assigned to the default control plane:
      curl --request POST \
     --url https://{region}.api.konghq.com/v2/control-planes/{defaultControlPlaneId}/core-entities/services \
     --header 'Authorization: Bearer <personal-access-token>' \
     --header 'Content-Type: application/json' \
     --header 'accept: application/json' \
     --data '{
         "name": "my_service",
         "host": "httpbin.konghq.com",
         "path": "/mock"
     }'
    

    This service represents your backend API. Be sure to replace the PAT as well as the following placeholders with your own values:

    • defaultControlPlaneId: The ID of the default control plane. This associates the service with that control plane.
    • name: The name you want to display for your service.
    • host: The host of the upstream server. This is case sensitive.
    • path: The path to be used in requests to the upstream server. Be sure to save the service ID from the response to use it in the next step.
  3. Add a route to your service:
      curl --request POST \
     --url https://{region}.api.konghq.com/v2/control-planes/{defaultControlPlaneId}/core-entities/routes \
     --header 'Authorization: Bearer <personal-access-token>' \
     --header 'Content-Type: application/json' \
     --header 'accept: application/json' \
     --data '{
         "name": "my_route",
         "hosts": [
           "httpbin.konghq.com"
         ],
         "paths": [
           "/mock"
         ],
         "service": {
           "id": "49248arf-b90c-4c0b-9529-3a949dfc10d1"
         }
     }'
    

    This route defines what is exposed to clients. Be sure to replace the PAT as well as the following placeholders with your own values:

    • defaultControlPlaneId: The ID of the default control plane. This associates the service with that control plane.
    • name: The name you want to display for your route.
    • host: A list of domain names that match this route. This is case sensitive.
    • path: A list of paths that match this route.
    • "service": "id": The ID of the service you created in the previous step. This should be part of the response from the previous request.

Verify the implementation

If you used the Docker script to connect a data plane earlier, your default proxy URL is localhost:8000.

Enter the proxy URL into your browser’s address bar and append the route path you just set. The final URL should look something like this:

http://localhost:8000/mock

If successful, you should see the homepage for httpbin.konghq.com. In the Gateway Manager you will now see a 200 responses recorded in the Analytics tab.

And that’s it! You have your first service set up, running, and routing traffic proxied through a Kong Gateway data plane node.

Important: To conserve your free trial credits, delete any APIs you don’t plan to use in production.

Next steps

Now that you’ve added your API to Konnect, you can continue to test Konnect’s capabilities:

Protect my APIs with key authentication
Rate limit my APIs
Make my APIs available to customers
Thank you for your feedback.
Was this page useful?
情報が多すぎる場合 close cta icon
Kong Konnectを使用すると、より多くの機能とより少ないインフラストラクチャを実現できます。月額1Mリクエストが無料。
無料でお試しください
  • Kong
    APIの世界を動かす

    APIマネジメント、サービスメッシュ、イングレスコントローラーの統合プラットフォームにより、開発者の生産性、セキュリティ、パフォーマンスを大幅に向上します。

    • 製品
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • 製品アップデート
      • 始める
    • ドキュメンテーション
      • Kong Konnectドキュメント
      • Kong Gatewayドキュメント
      • Kong Meshドキュメント
      • Kong Insomniaドキュメント
      • Kong Konnect Plugin Hub
    • オープンソース
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kongコミュニティ
    • 会社概要
      • Kongについて
      • お客様
      • キャリア
      • プレス
      • イベント
      • お問い合わせ
  • 利用規約• プライバシー• 信頼とコンプライアンス
© Kong Inc. 2025