OpenAPI endpoint shows up in the schema but not in the dropdown?

Queries and Resources
, ,
1

  • Goal:
    Just trying to access an endpoint in our OpenAPI resource.

  • Steps:

  1. Create a new resource query
  2. Select the OpenAPI resource
  3. Observe that the endpoint is visible in the Schema of the resource
  4. Try to type the name of the resource in Operation with no results
  5. Try refreshing the schema
  6. Try using the workaround where you edit the resource and check/uncheck "Forward all cookies" to try and force a refresh

Here is what this endpoint looks like in our OpenAPI spec:

{
  "/admin/v1/me/sendbird/token/issue": {
    "post": {
      "operationId": "PostAdminV1MeSendbirdTokenIssue",
      "requestBody": {
        "description": "POST /admin/v1/me/sendbird/token/issue Request body",
        "content": {
          "application/json": {
            "schema": {
              "type": "object"
            }
          }
        }
      },
      "responses": {
        "200": {
          "description": "POST /admin/v1/me/sendbird/token/issue Positive response",
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "status": {
                    "type": "string",
                    "const": "success"
                  },
                  "data": {
                    "type": "object",
                    "properties": {
                      "sendbirdSessionToken": {
                        "type": "string"
                      },
                      "expiresAt": {
                        "type": "integer",
                        "format": "int64",
                        "minimum": -9007199254740991,
                        "maximum": 9007199254740991
                      }
                    },
                    "required": [
                      "sendbirdSessionToken",
                      "expiresAt"
                    ]
                  }
                },
                "required": [
                  "status",
                  "data"
                ]
              }
            }
          }
        },
        "400": {
          "description": "POST /admin/v1/me/sendbird/token/issue Negative response",
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "status": {
                    "type": "string",
                    "const": "error"
                  },
                  "error": {
                    "type": "object",
                    "properties": {
                      "message": {
                        "type": "string"
                      }
                    },
                    "required": [
                      "message"
                    ]
                  }
                },
                "required": [
                  "status",
                  "error"
                ]
              },
              "examples": {
                "example1": {
                  "value": {
                    "status": "error",
                    "error": {
                      "message": "Sample error message"
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}
1 Like
2

Hello @topherauyeung if you click the dropdown for the operation with an empty value, do you see any options? Also, if you use the operationId (PostAdminV1MeSendbirdTokenIssue) instead of the URL, is the result the same?

3

We see all of the other endpoints just fine, it's just the one I posted that's missing. Using PostAdminV1MeSendbirdTokenIssue doesn't show the endpoint either unfortunately.

4

As an additional data point, we just added 2 more endpoints to the admin/v1/me namespace and those are also not showing up in the dropdown.

EDIT: the two additional endpoints just showed up but the original endpoint still has not shown up

5

:thinking: Are you able to share the spec with me so that we can research internally?

Are you able to query this endpoint using the REST api integration for the time being?

Are there any browser console errors?