ChatGPT cannot call Action (custom REST endpoint)

GPT builders Plugins / Actions builders
1

Hello,
I have created a simple public REST endpoint that I want to be called by my custom ChatGPT. However it never succeeds, as shown from screenshot. It is not using the correct endpoint name it seems.

chataction_error
chataction_error1340×1166 61.7 KB

The endpoints is like …/words/STRING and returns a json array.

Below is the OpenAPI spec, which is correct. I imported it in Postman and the generated request works as expected.

Appreciate your help.

Thanks,
Andreas

openapi: 3.0.0
info:
  title: Words API
  version: 1.0.0
  description: API to find words matching a given character string
servers:
  - url: https://kibokaj.pythonanywhere.com/
    description: Production server

paths:
  /words/{charstring}:
    get:
      summary: Retrieve words containing specific characters
      description: >
        This endpoint returns a list of words that contain the characters
        provided in the order specified by 'charstring'. The characters may be
        separated by other characters in the words.
      parameters:
        - in: path
          name: charstring
          required: true
          schema:
            type: string
          description: The character string to find in words
      responses:
        '200':
          description: A list of words matching the character string
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
        '400':
          description: Bad request (e.g., no character string provided)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
2

I’m facing the same issue.

@andreas.jakobik you can validate openapi scheme with Postman, but I bet it is correct.

I’m waiting some reaction from Open AI for 3 hours yet.

1 Like
3

same issue.
Seems that actions with parameters (path variables or query parameters) do not work.
Although the requests without any parameters worked fine