> ## Documentation Index
> Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong.
> Authenticate every request with `Authorization: Bearer <API_KEY>`. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test.
> Send with `client.send.message` from the Node SDK (`@trycourier/courier` v7 and later, where the client is the default import). Reference a template by its `nt_` id or its alias.
> A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element.
> Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send.
> The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt.
> Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference.

# List Preview Devices

> List the devices a preview can be rendered on. Reference data, identical for every workspace — these ids are what a device set is built from and what a run reports results for.



## OpenAPI

````yaml /openapi-specs/openapi.documented.yml get /previews/devices
openapi: 3.0.1
info:
  title: Courier
  description: The Courier REST API for sending and managing notifications across channels.
  version: 0.0.1
servers:
  - url: https://api.courier.com
    description: Production
security: []
tags:
  - name: Send
    description: >-
      Send a message to one or more recipients — users, lists, audiences, or
      tenants — across every channel you have configured.
  - name: Templates
    description: >-
      Create, update, version, publish, and localize notification templates and
      their content.
  - name: Brands
    description: >-
      Manage the logos, colors, and layout that give the templates you send a
      consistent look.
  - name: Routing Strategies
    description: >-
      Define reusable channel routing and failover strategies, and see which
      templates use them.
  - name: Journeys
    description: >-
      Build, version, publish, invoke, and cancel multi-step notification
      workflows, along with the templates scoped to them.
  - name: Broadcasts
    description: >-
      Create a one-off send to a list or audience, author its content, then send
      it immediately or schedule it for later.
  - name: Previews
    description: >-
      Render a template's email content on real email clients and read back the
      screenshots, so you can check how it looks before you send it.
  - name: User Profiles
    description: >-
      Store the contact information Courier delivers to for each user — email,
      phone number, push tokens, and any custom data you send to.
  - name: Tenants
    description: >-
      Manage tenants — the organizations, teams, or accounts your users belong
      to — along with their users and default preferences.
  - name: Audiences
    description: >-
      Define filter-based groups whose membership Courier recalculates as user
      profiles change.
  - name: Lists
    description: >-
      Manage static groups of users that you subscribe explicitly, and send to
      them by list id or list pattern.
  - name: Providers
    description: >-
      Configure the channel providers Courier delivers through, and browse the
      provider types it supports.
  - name: Preference Topics
    description: >-
      Manage the workspace catalog of subscription topics, the sections that
      group them, and publishing the preference page.
  - name: User Preferences
    description: >-
      Read and write a single user's notification preferences, per topic and per
      channel.
  - name: Messages
    description: >-
      Look up the messages Courier has accepted, inspect their delivery history
      and rendered output, and cancel, resend, or archive them.
  - name: Device Tokens
    description: >-
      Register and manage the APNS and FCM device tokens Courier delivers push
      notifications to.
  - name: Tenant Memberships
    description: >-
      Associate a user with one or more tenants, and read or remove those
      associations.
  - name: Tenant Templates
    description: >-
      Manage the templates and template versions scoped to a single tenant,
      including the ones authored in the embedded designer.
  - name: Automations
    description: >-
      Invoke a stored automation template or an ad hoc automation defined in the
      request.
  - name: Digests
    description: >-
      Inspect what has accumulated in a digest schedule and release a digest
      ahead of its next scheduled delivery.
  - name: Translations
    description: >-
      Store and retrieve the translation strings Courier uses to render
      localized template content.
  - name: Track Events
    description: >-
      Record an inbound event that triggers the journeys and automations mapped
      to it.
  - name: Audit Events
    description: >-
      Read the audit trail of configuration and access changes in your
      workspace.
  - name: Authentication
    description: >-
      Issue scoped, short-lived JWTs so client-side SDKs — Inbox, Preferences,
      and the embedded designer — can call Courier as a single user. Server-side
      requests authenticate with your workspace API key instead.
paths:
  /previews/devices:
    get:
      tags:
        - Previews
      summary: List Preview Devices
      description: >-
        List the devices a preview can be rendered on. Reference data, identical
        for every workspace — these ids are what a device set is built from and
        what a run reports results for.
      operationId: previews_list_devices
      parameters: []
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PreviewDeviceListResponse'
              examples:
                Example:
                  value:
                    results:
                      - id: pvd_34qvmj6p4dbqaa5mpys1ekt9jx
                        name: Outlook.com (Firefox, Windows 10, dark mode)
                        category: webmail
                        app: outlook_com
                        platform: firefox
                        platform_version: null
                        os: windows
                        os_version: '10'
                        theme: dark
                      - id: pvd_1w6dgafr3aaycvv9a8bm996pkc
                        name: Apple Mail (iPhone 15 Pro Max, iOS 17, dark mode)
                        category: mobile
                        app: apple_mail
                        platform: iphone
                        platform_version: 15_pro_max
                        os: ios
                        os_version: '17'
                        theme: dark
      security:
        - BearerAuth: []
      x-codeSamples:
        - lang: JavaScript
          source: >-
            import Courier from '@trycourier/courier';


            const client = new Courier({
              apiKey: process.env['COURIER_API_KEY'], // This is the default and can be omitted
            });


            const previewDeviceListResponse = await
            client.previews.listDevices();


            console.log(previewDeviceListResponse.results);
        - lang: Python
          source: |-
            import os
            from courier import Courier

            client = Courier(
                api_key=os.environ.get("COURIER_API_KEY"),  # This is the default and can be omitted
            )
            preview_device_list_response = client.previews.list_devices()
            print(preview_device_list_response.results)
        - lang: Go
          source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/trycourier/courier-go/v4\"\n\t\"github.com/trycourier/courier-go/v4/option\"\n)\n\nfunc main() {\n\tclient := courier.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tpreviewDeviceListResponse, err := client.Previews.ListDevices(context.TODO())\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", previewDeviceListResponse.Results)\n}\n"
        - lang: Java
          source: |-
            package com.courier.example;

            import com.courier.client.CourierClient;
            import com.courier.client.okhttp.CourierOkHttpClient;
            import com.courier.models.previews.PreviewDeviceListResponse;
            import com.courier.models.previews.PreviewListDevicesParams;

            public final class Main {
                private Main() {}

                public static void main(String[] args) {
                    CourierClient client = CourierOkHttpClient.fromEnv();

                    PreviewDeviceListResponse previewDeviceListResponse = client.previews().listDevices();
                }
            }
        - lang: Ruby
          source: |-
            require "courier"

            courier = Courier::Client.new(api_key: "My API Key")

            preview_device_list_response = courier.previews.list_devices

            puts(preview_device_list_response)
        - lang: PHP
          source: >-
            <?php


            require_once dirname(__DIR__) . '/vendor/autoload.php';


            use Courier\Client;

            use Courier\Core\Exceptions\APIException;


            $client = new Client(apiKey: getenv('COURIER_API_KEY') ?: 'My API
            Key');


            try {
              $previewDeviceListResponse = $client->previews->listDevices();

              var_dump($previewDeviceListResponse);
            } catch (APIException $e) {
              echo $e->getMessage();
            }
        - lang: C#
          source: >-
            using System;

            using TryCourier;

            using TryCourier.Models.Previews;


            CourierClient client = new();


            PreviewListDevicesParams parameters = new();


            var previewDeviceListResponse = await
            client.Previews.ListDevices(parameters);


            Console.WriteLine(previewDeviceListResponse);
        - lang: CLI
          source: |-
            courier previews list-devices \
              --api-key 'My API Key'
components:
  schemas:
    PreviewDeviceListResponse:
      title: PreviewDeviceListResponse
      type: object
      description: The full catalog of renderable devices. Not paginated.
      properties:
        results:
          type: array
          items:
            $ref: '#/components/schemas/PreviewDevice'
      required:
        - results
    PreviewDevice:
      title: PreviewDevice
      type: object
      description: >-
        One mail app on one platform, operating system and theme that a preview
        can be rendered on. Reference data, identical for every workspace. Every
        field is always present; `platform` and `platform_version` are null
        where they do not apply.
      properties:
        id:
          type: string
          description: >-
            The device's identifier, used in `device_ids` when creating a device
            set or a run.
          example: pvd_2tecf6d6pybbvvnkdr0hwdpaxf
        name:
          type: string
          description: >-
            Display name. Render it as-is rather than parsing it. It is also
            what separates the two 120-dpi Outlook renders from their 100%
            siblings, which are otherwise identical field for field.
          example: Outlook.com (Firefox, Windows 10, dark mode)
        category:
          type: string
          description: Where the app runs.
          enum:
            - webmail
            - mobile
            - desktop
        app:
          type: string
          description: >-
            The mail app. For webmail it is the service (`outlook_com`,
            `gmail_com`); for mobile the app (`apple_mail`, `gmail`); for
            desktop the app together with the version it is sold under
            (`outlook_2019`, `outlook_microsoft_365`, `apple_mail_16`), because
            that version is what separates one desktop Outlook from another.
          example: outlook_com
        platform:
          type: string
          nullable: true
          description: >-
            What the app runs on — the browser for webmail (`chrome`, `edge`,
            `firefox`), the phone for mobile (`iphone`, `pixel`). Null for
            desktop, where the app runs on nothing but the OS.
          example: firefox
        platform_version:
          type: string
          nullable: true
          description: >-
            Which one of the platform — the phone model for mobile
            (`15_pro_max`, `10`). Null for webmail, which always renders in the
            current browser, and for desktop.
          example: 15_pro_max
        os:
          type: string
          description: The operating system.
          example: windows
        os_version:
          type: string
          description: The operating system's version. Always set.
          example: '10'
        theme:
          type: string
          description: Whether the email is rendered in light or dark mode.
          enum:
            - light
            - dark
      required:
        - id
        - name
        - category
        - app
        - platform
        - platform_version
        - os
        - os_version
        - theme
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer

````