> ## 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. # Publish Notification Template > Publish a notification template. Publishes the current draft by default. Pass a version in the request body to publish a specific historical version. ## OpenAPI ````yaml /openapi-specs/openapi.documented.yml post /notifications/{id}/publish 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: 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: Inbox description: Manage the messages in a user's in-app inbox. - 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: /notifications/{id}/publish: post: tags: - Templates summary: Publish Notification Template description: >- Publish a notification template. Publishes the current draft by default. Pass a version in the request body to publish a specific historical version. operationId: notifications_publish parameters: - $ref: '#/components/parameters/IdempotencyKey' - $ref: '#/components/parameters/IdempotencyExpiration' - name: id in: path description: Template ID (nt_ prefix). required: true schema: type: string requestBody: required: false content: application/json: schema: $ref: '#/components/schemas/NotificationTemplatePublishRequest' examples: PublishDraft: summary: Publish the current draft (default) value: {} PublishSpecificVersion: summary: Publish a specific historical version (rollback) value: version: v001 responses: '204': description: >- Successfully published, or already published with no changes (idempotent). '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/BadRequest' examples: InvalidVersion: value: type: invalid_request_error message: 'version: Expected format: v001, v002, etc.' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/NotFound' examples: TemplateNotFound: value: type: invalid_request_error message: >- Notification template nt_01kx4kepxgfq9ty3r3wyf61n5t not found VersionNotFound: value: type: invalid_request_error message: >- Version not found for template nt_01kx4h2jdafq8bk9aftxak4b40 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 }); await client.notifications.publish('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 ) client.notifications.publish( id="id", ) - lang: Go source: "package main\n\nimport (\n\t\"context\"\n\n\t\"github.com/trycourier/courier-go\"\n\t\"github.com/trycourier/courier-go/option\"\n)\n\nfunc main() {\n\tclient := courier.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\terr := client.Notifications.Publish(\n\t\tcontext.TODO(),\n\t\t\"id\",\n\t\tcourier.NotificationPublishParams{},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n}\n" - lang: Java source: |- package com.courier.example; import com.courier.client.CourierClient; import com.courier.client.okhttp.CourierOkHttpClient; import com.courier.models.notifications.NotificationPublishParams; public final class Main { private Main() {} public static void main(String[] args) { CourierClient client = CourierOkHttpClient.fromEnv(); client.notifications().publish("id"); } } - lang: Ruby source: |- require "courier" courier = Courier::Client.new(api_key: "My API Key") result = courier.notifications.publish("id") puts(result) - lang: PHP source: >- notifications->publish( 'id', version: 'v321669910225', idempotencyKey: 'order-ORD-456-user-123', xIdempotencyExpiration: '1785312000', ); var_dump($result); } catch (APIException $e) { echo $e->getMessage(); } - lang: C# source: |- using TryCourier; using TryCourier.Models.Notifications; CourierClient client = new(); NotificationPublishParams parameters = new() { ID = "id" }; await client.Notifications.Publish(parameters); - lang: CLI source: |- courier notifications publish \ --api-key 'My API Key' \ --id id components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- A unique key that makes this request idempotent. If Courier receives another request with the same `Idempotency-Key`, it returns the stored response from the first request without performing the operation again (including the original status code and any error). Use it to safely retry `POST` requests after network failures without risking duplicate sends. The key is scoped to this endpoint. schema: type: string example: order-ORD-456-user-123 IdempotencyExpiration: name: x-idempotency-expiration in: header required: false description: >- How long the idempotency key remains valid, as a Unix epoch timestamp in seconds or an ISO 8601 date string. Only applies when `Idempotency-Key` is provided. If omitted, the key is retained for 25 hours; the maximum is 1 year. schema: type: string example: '1785312000' schemas: NotificationTemplatePublishRequest: title: NotificationTemplatePublishRequest type: object description: >- Optional request body for publishing a notification template. Omit or send an empty object to publish the current draft. properties: version: type: string pattern: ^v\d+$ description: >- Historical version to publish (e.g. "v001"). Omit to publish the current draft. BadRequest: title: BadRequest type: object properties: type: type: string enum: - invalid_request_error required: - type allOf: - $ref: '#/components/schemas/BaseError' NotFound: title: NotFound 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 ````