Hello Apidog Support,

We are importing our API definition from an OpenAPI 3.0.3 specification.

We have several request header parameters where the schema is referenced via $ref. The referenced schema is a string enum, and it also contains the x-apidog-enum extension with names and descriptions.

Example:

parameters:

- in: header

name: x-custom-source

required: true

schema:

$ref: '#/components/schemas/SourceSystemEnum'

components:

schemas:

SourceSystemEnum:

description: Source system identifier

type: string

enum:

- system-a

- system-b

example: system-a

x-apidog-enum:

- value: system-a

name: System A

description: Example source system A

- value: system-b

name: System B

description: Example source system B

After importing the OpenAPI file, the schema itself is recognized correctly in Apidog: if we open the schema/model, the field is shown as an enum and the enum values are visible.

However, when we open an endpoint and try to execute a request in the UI, the request header field is displayed as a simple text input. It does not appear as a dropdown with the possible enum values.

Could you please confirm whether Apidog supports dropdown rendering for request header parameters when the enum schema is referenced via $ref and includes x-apidog-enum?

If this is supported, could you let us know what the expected OpenAPI structure should be?

Thank you.