GPT Actions Custom API Key header returns 400

GPT builders Plugins / Actions builders
,
1

Hi everyone.

I’m trying to call the Kintone REST API from a Custom GPT Action using Kintone API token authentication. But it wasn’t work.

Kintone expects the API token in this header:

X-Cybozu-API-Token: <API_TOKEN>

In the GPT Action authentication settings, I configured:

Authentication Type: API Key
Auth Type: Custom
Custom Header Name: X-Cybozu-API-Token
API Key: <Kintone API token>

The Action calls:

GET https://sample.cybozu.com/k/v1/records.json?app=3

However, Kintone always returns 400 Error.
When I confirmed postman and curl command, they alewys succeeds with HTTP 200.

My OpenAPI security definition is:

components:
  securitySchemes:
    KintoneApiToken:
      type: apiKey
      in: header
      name: X-Cybozu-API-Token

paths:
  /k/v1/records.json:
    get:
      security:
        - KintoneApiToken: []

The GPT Action execution log shows:

{
  "domain": "sample.cybozu.com",
  "method": "get",
  "path": "/k/v1/records.json",
  "operation": "getKintoneRecords",
  "params": {
    "app": 3
  }
}

So far I have confirmed:

  • The Kintone API token is valid.
  • App ID 3 is correct.
  • The token has record read permission.
  • The URL is correct.
  • The same request succeeds using curl.
  • OAS succeeds using Postman.

Has anyone successfully used GPT Actions with a custom API-key header such as X-Cybozu-API-Token?

Is there any difference in how GPT Actions sends a Custom API Key header compared with curl, or any known restriction on headers beginning with X-?

Any suggestions for inspecting the actual outbound request headers from GPT Actions would also be helpful.

2

I think this is a same issue.