> ## 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 `. 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. # Archive Device Set > Archive a device set. This is a soft delete — the archived set is returned and no longer appears in list results. Runs already created against it keep their own copy of the device list and are unaffected. The Courier-provided default set cannot be archived and returns 409. ## OpenAPI ````yaml /openapi-specs/openapi.documented.yml delete /previews/device-sets/{deviceSetId} 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/device-sets/{deviceSetId}: delete: tags: - Previews summary: Archive Device Set description: >- Archive a device set. This is a soft delete — the archived set is returned and no longer appears in list results. Runs already created against it keep their own copy of the device list and are unaffected. The Courier-provided default set cannot be archived and returns 409. operationId: previews_archive_device_set parameters: - name: deviceSetId in: path description: The preview set to archive. required: true schema: type: string responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/DeviceSet' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/NotFound' '409': description: >- Conflict — this is the Courier-provided default device set ("Courier Recommended"), which cannot be changed or archived. Create your own set instead. content: application/json: schema: $ref: '#/components/schemas/Conflict' examples: DefaultDeviceSet: value: type: invalid_request_error message: >- device set pvs_01m2np6evsfam98rf7t6a2k6n1 is the Courier default set and cannot be changed or archived 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 deviceSet = await client.previews.archiveDeviceSet('deviceSetId'); console.log(deviceSet.id); - 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 ) device_set = client.previews.archive_device_set( "deviceSetId", ) print(device_set.id) - 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\tdeviceSet, err := client.Previews.ArchiveDeviceSet(context.TODO(), \"deviceSetId\")\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", deviceSet.ID)\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.DeviceSet; import com.courier.models.previews.PreviewArchiveDeviceSetParams; public final class Main { private Main() {} public static void main(String[] args) { CourierClient client = CourierOkHttpClient.fromEnv(); DeviceSet deviceSet = client.previews().archiveDeviceSet("deviceSetId"); } } - lang: Ruby source: |- require "courier" courier = Courier::Client.new(api_key: "My API Key") device_set = courier.previews.archive_device_set("deviceSetId") puts(device_set) - lang: PHP source: >- previews->archiveDeviceSet('deviceSetId'); var_dump($deviceSet); } catch (APIException $e) { echo $e->getMessage(); } - lang: C# source: |- using System; using TryCourier; using TryCourier.Models.Previews; CourierClient client = new(); PreviewArchiveDeviceSetParams parameters = new() { DeviceSetID = "deviceSetId" }; var deviceSet = await client.Previews.ArchiveDeviceSet(parameters); Console.WriteLine(deviceSet); - lang: CLI source: |- courier previews archive-device-set \ --api-key 'My API Key' \ --device-set-id deviceSetId components: schemas: DeviceSet: title: DeviceSet type: object description: A named, reusable list of preview devices. properties: id: type: string description: Unique identifier for the device set. name: type: string description: Human-readable name. device_ids: type: array description: The devices in this set, by `PreviewDevice.id`. items: type: string created_at: type: string description: ISO-8601 timestamp of when the set was created. updated_at: type: string description: ISO-8601 timestamp of when the set was last written. archived_at: type: string description: >- ISO-8601 timestamp of when the set was archived. Present only on the archive response, which is the one place the state is observable. required: - id - name - device_ids - created_at - updated_at NotFound: title: NotFound type: object properties: type: type: string enum: - invalid_request_error required: - type allOf: - $ref: '#/components/schemas/BaseError' Conflict: title: Conflict type: object properties: type: type: string enum: - invalid_request_error required: - type allOf: - $ref: '#/components/schemas/BaseError' BaseError: title: BaseError type: object properties: message: type: string description: A message describing the error that occurred. required: - message securitySchemes: BearerAuth: type: http scheme: bearer ````