> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://buildwithfern.com/learn/llms.txt.

# Use audiences to filter your API

#### Enterprise feature for SDKs

Using this feature in generated SDKs requires the [Enterprise plan](https://buildwithfern.com/pricing). To get started, reach out to [support@buildwithfern.com](mailto:support@buildwithfern.com).

Audiences are a useful tool for segmenting your event-driven API for different consumers. Common examples of audiences include `public`
and `beta`.

Tag operations, channels, and message schemas with `x-fern-audiences`, then filter each output to those audiences: [SDKs in `generators.yml`](/learn/sdks/deep-dives/audiences) and your [API Reference in `docs.yml`](/learn/docs/api-references/audiences). Untagged elements are always included; if you don't specify audiences, nothing is filtered.

## Filter operations

Add `x-fern-audiences` to operations to control which operations are included for specific audiences:

**`asyncapi.yml`**

```yaml title="asyncapi.yml" {5-6, 12-13}
operations:
  sendPublicNotification:
    action: send
    channel:
      $ref: '#/channels/public~1notifications'
    x-fern-audiences:
      - public
  sendBetaAlert:
    action: send
    channel:
      $ref: '#/channels/beta~1alerts'
    x-fern-audiences:
      - beta
```

## Filter channels

You can also filter entire channels by audience:

**`asyncapi.yml`**

```yaml title="asyncapi.yml" {6-7, 13-14}
channels:
  public/events:
    address: public/events
    messages:
      PublicEvent:
        $ref: '#/components/messages/PublicEvent'
    x-fern-audiences:
      - public
  internal/events:
    address: internal/events
    messages:
      InternalEvent:
        $ref: '#/components/messages/InternalEvent'
    x-fern-audiences:
      - internal
```

## Filter message schemas

Filter specific message schemas to different audiences:

**`asyncapi.yml`**

```yaml title="asyncapi.yml" {5-6, 13-14}
components:
  messages:
    PublicUserEvent:
      contentType: application/json
      payload:
        $ref: '#/components/schemas/PublicUser'
      x-fern-audiences:
        - public
    AdminUserEvent:
      contentType: application/json
      payload:
        $ref: '#/components/schemas/AdminUser'
      x-fern-audiences:
        - admin
  schemas:
    PublicUser:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        email:
          type: string
      x-fern-audiences:
        - public
    AdminUser:
      allOf:
        - $ref: '#/components/schemas/PublicUser'
        - type: object
          properties:
            role:
              type: string
            permissions:
              type: array
              items:
                type: string
      x-fern-audiences:
        - admin
```

## Filter schema properties

You can filter individual properties within schemas:

**`asyncapi.yml`**

```yaml title="asyncapi.yml" {9-10, 13-14}
components:
  schemas:
    UserEvent:
      type: object
      properties:
        id:
          type: string
        email:
          type: string
          x-fern-audiences:
            - internal
        publicName:
          type: string
          x-fern-audiences:
            - public
        internalNotes:
          type: string
          x-fern-audiences:
            - internal
```

This allows you to have different views of the same event schema for different audiences, showing only the relevant information to each consumer.

> Use `x-fern-audiences` to filter to relevant operations, channels and message schemas