### Define Global Headers with `x-is-global-header`

Source: https://github.com/neynarxyz/oas/blob/main/contribution.md

Provides an example of defining a global header in OpenAPI 3.1.0 using the `x-is-global-header: true` vendor extension. This ensures the header is consistently applied across all API operations.

```yaml
parameters:
  NeynarExperimentalHeader:
    name: x-neynar-experimental
    in: header
    required: false
    schema:
      type: boolean
      default: false
    description: "Enables experimental features"
    x-is-global-header: true
```

--------------------------------

### Tag Naming Convention in OpenAPI

Source: https://github.com/neynarxyz/oas/blob/main/contribution.md

Illustrates the convention of using `PascalCase` for API tags within an OpenAPI specification. This promotes a consistent and readable structure for API grouping.

```yaml
tags:
  - HubEvents
```

--------------------------------

### Identify Limit Parameters with `x-is-limit-param`

Source: https://github.com/neynarxyz/oas/blob/main/contribution.md

Shows how to mark a parameter as a limit parameter using `x-is-limit-param: true`. This allows the SDK to automatically handle default and maximum values defined within the OAS for limit-related parameters.

```yaml
parameters:
  - name: limit
    in: query
    required: false
    description: Number of users to fetch
    example: 10
    schema:
      type: integer
      format: int32
      default: 5
      minimum: 1
      maximum: 10
    x-is-limit-param: true
```

--------------------------------

### Type Conversion with `x-accept-as` Vendor Extension

Source: https://github.com/neynarxyz/oas/blob/main/contribution.md

Illustrates the use of the `x-accept-as` vendor extension to specify a different data type for a parameter than what the API fundamentally expects. In this example, a string parameter `fids` is accepted as an integer.

```yaml
parameters:
  - name: fids
    description: Comma separated list of FIDs, up to 100 at a time
    in: query
    required: true
    example: 194, 191, 6131
    schema:
      type: string
      x-comma-separated: true
      x-accept-as: integer
```

--------------------------------

### Handle Comma-Separated Values with `x-comma-separated`

Source: https://github.com/neynarxyz/oas/blob/main/contribution.md

Demonstrates how to use the `x-comma-separated: true` vendor extension in OpenAPI 3.1.0 to indicate that a string parameter should be treated as a comma-separated list. This is useful for parameters like FID lists.

```yaml
parameters:
  - name: fids
    description: Comma separated list of FIDs, up to 100 at a time
    in: query
    required: true
    example: 194, 191, 6131
    schema:
      type: string
      x-comma-separated: true
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.