Migration IBM API Connect → Kong Konnect
This guide walks you through migrating your integrations from the IBM API Connect portal to the new Kong Konnect portal.
Summary of Changes
| Element | IBM API Connect | Kong Konnect |
|---|---|---|
| Base URL | https://api.stef.com/ | https://api.stef.com/ |
| Authentication | Client ID / Secret IBM | OAuth 2.0 / API Key Kong |
| Gateway | DataPower | Kong Gateway |
| Portal | Drupal (connect_theme) | Kong Dev Portal v3 (MDC) |
| Specifications | Swagger 2.0 | OpenAPI 3.0 |
| Rate limiting | Plan-based | Plugin-based (configurable) |
Step 1: New Credentials
Your existing IBM API Connect credentials continue to work for already active subscriptions.
However, for any new API subscription, you must:
- Create an account on the new portal (if not done yet)
- Create a new application
- Subscribe to the desired APIs
- Retrieve your new credentials (API Key)
Step 2: Error Handling
The error format has changed:
Old IBM Format
{
"httpCode": "404",
"httpMessage": "Not Found",
"moreInformation": "Resource not found"
}
New Kong Format
{
"status": 404,
"title": "Not Found",
"detail": "The requested resource was not found",
"instance": "/v1/transport/orders/invalid-id"
}
Migration Checklist
- Create a new account on the Kong portal
- Create an application and retrieve credentials
- Adapt error parsing to the new format
Migration Support
Need help migrating?
Our support team is available to assist you with your migration. Do not hesitate to contact us.