Kong/insomnia · error

Unable to parse additional-claims: ${err}

Error message

Unable to parse additional-claims: ${err}

What it means

Error "Unable to parse additional-claims: ${err}" thrown in Kong/insomnia.

Source

Thrown at packages/insomnia/src/main/network/get-auth-header.ts:147

    }
    return {
      header: {
        name: 'Authorization',
        value: Hawk.client.header(url, method, {
          ...headerOptions,
          payload: renderedRequest.body.text,
          contentType: renderedRequest.body.mimeType || undefined,
        }).header,
      },
    };
  }

  if (authentication.type === 'asap') {
    let parsedAdditionalClaims;
    try {
      parsedAdditionalClaims = JSON.parse(authentication.additionalClaims || '{}');
    } catch (err) {
      throw new Error(`Unable to parse additional-claims: ${err}`);
    }

    if (parsedAdditionalClaims && typeof parsedAdditionalClaims !== 'object') {
      throw new Error(`additional-claims must be an object received: '${typeof parsedAdditionalClaims}' instead`);
    }

    const generator = (await import('httplease-asap')).createAuthHeaderGenerator({
      privateKey: authentication.privateKey,
      issuer: authentication.issuer,
      keyId: authentication.keyId,
      audience: authentication.audience,
      subject: authentication.subject,
      additionalClaims: parsedAdditionalClaims,
      tokenExpiryMs: 10 * 60 * 1000,
      tokenMaxAgeMs: 9 * 60 * 1000,
    });
    return {
      header: {

View on GitHub (pinned to d9bb2b0142)

When it happens

Trigger: Thrown at packages/insomnia/src/main/network/get-auth-header.ts:147 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.

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