Kong/insomnia · error

Konnect API error fetching control planes

Error message

Konnect API error ${response.status} fetching control planes

What it means

Konnect API pagination error in fetchAllControlPlanes: the control-planes endpoint responded with a non-OK HTTP status while iterating pages. The HTTP status code is interpolated; see the response body/logs for Konnect's error detail.

Solutions

1. Verify the Konnect PAT is valid and has the right roles
2. Check the selected region URL is correct
3. Retry later if the API returns a transient 5xx

When it happens

Trigger: Thrown at packages/insomnia/src/konnect/api.ts:171 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of Kong/insomnia@d9bb2b0142 (2026-08-26). Data as JSON: /api/errors/53d0c91bbecf6fa9. Report an issue: GitHub.

Appendix: source

Thrown at packages/insomnia/src/konnect/api.ts:171

  } catch {
    return undefined;
  }
}

export async function* fetchAllControlPlanes(
  pat: string,
  region: KonnectRegion,
  signal?: AbortSignal,
): AsyncGenerator<KonnectControlPlane[]> {
  let page = 1;
  let totalPages = 1;

  do {
    const url = `${regionalApiBase(region)}/v2/control-planes?page[size]=${PAGE_SIZE}&page[number]=${page}`;
    const response = await fetchWithRetry(url, pat, signal);

    if (!response.ok) {
      throw new Error(`Konnect API error ${response.status} fetching control planes`);
    }

    const body = await response.json();
    const total: number = body?.meta?.page?.total ?? 0;
    totalPages = Math.ceil(total / PAGE_SIZE) || 1;

    yield (body.data as KonnectControlPlane[]).map(cp => normalizeControlPlane(cp, region));
    page++;
  } while (page <= totalPages);
}

async function fetchAllOffsetPaginated<T>(
  baseUrl: string,
  pat: string,
  errorContext: string,
  signal?: AbortSignal,
): Promise<T[]> {
  const results: T[] = [];

View on GitHub (pinned to d9bb2b0142)