How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Courier

Courier Notification Templates API

The Notification Templates API from Courier — 8 operation(s) for notification templates.

Documentation Provider Profile APIs.io OpenAPI GitHub

Courier Notification Templates API is one of 22 APIs that Courier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Notification Templates. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 14 operations across 8 paths, and defines 55 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.courier.com.

14 operations 8 paths 55 schemas 2 DELETE5 GET2 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.courier.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Courier Notification Templates API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 14

Across 8 paths, the API surfaces 14 operations — 2 DELETE, 5 GET, 2 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Notification Templates 14
GET
/notifications
List Notification Templates
notifications_list 3 params → 200
POST
/notifications
Create Notification Template
notifications_create body → 201400
GET
/notifications/{id}
Get Notification Template
notifications_retrieve 2 params → 200404
PUT
/notifications/{id}
Replace Notification Template
notifications_replace 1 param body → 200400404
DELETE
/notifications/{id}
Archive Notification Template
notifications_archive 1 param → 204404
GET
/notifications/{id}/versions
List Notification Template Versions
notifications_listVersions 3 params → 200400404
POST
/notifications/{id}/publish
Publish Notification Template
notifications_publish 1 param body → 204400404
GET
/notifications/{id}/content
Get Notification Content
notifications_getContent 2 params → 200404
PUT
/notifications/{id}/content
Put Notification Content
notifications_putContent 1 param body → 200400404
PUT
/notifications/{id}/elements/{elementId}
Put Notification Element
notifications_putElement 2 params body → 200400404
PUT
/notifications/{id}/locales/{localeId}
Put Notification Locale
notifications_putLocale 2 params body → 200400404
GET
/notifications/{id}/{submissionId}/checks
Get Submission Checks
notifications_getSubmissionChecks 2 params → 200
PUT
/notifications/{id}/{submissionId}/checks
Replace Submission Checks
notifications_replaceSubmissionChecks 2 params body → 200
DELETE
/notifications/{id}/{submissionId}/checks
Cancel Submission
notifications_cancelSubmission 2 params → 204

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are ElementalTextNode (10 properties), Notification (9 properties), NotificationTemplateSummary (8 properties), NotificationElementPutRequest (7 properties). Each schema is shown below with its type and property counts.

ElementWithChecksums
object
An element with its content checksum and optional nested elements and locale checksums.
5 properties 2 required
ElementalNode
NotificationTemplateSummary
object
V2 (CDS) template summary returned in list responses.
8 properties 6 required
ElementalChannelNode
object
The channel element allows a notification to be customized based on which channel it is sent through. For example, you may want to display a detailed message w…
2 properties
NotificationTag
object
1 property 1 required
BaseCheck
object
3 properties 3 required
CheckStatus
string
SubmissionChecksReplaceResponse
object
1 property 1 required
NotificationGetContentResponse
object
3 properties
Check
object
1 property 1 required
NotificationListResponse
object
2 properties 2 required
MessageRouting
object
2 properties 2 required
BadRequest
object
1 property 1 required
NotificationBlock
object
7 properties 2 required
NotificationTemplatePayload
object
Core template fields used in POST and PUT request bodies (nested under a notification key) and returned at the top level in responses.
6 properties 6 required
NotificationContentGetResponse
object
Elemental content response for V2 templates. Contains versioned elements with content checksums.
2 properties 2 required
NotificationContentPutRequest
object
Request body for replacing the elemental content of a notification template.
2 properties 1 required
NotificationTemplateUpdateRequest
object
Request body for replacing a notification template. Same shape as create. All fields required (PUT = full replacement).
2 properties 1 required
ElementalBaseNode
object
4 properties
ElementalContent
object
2 properties 2 required
ElementalTextNode
object
Represents a body of text to be rendered inside of the notification.
10 properties 2 required
ElementalHtmlNode
object
Raw HTML string inside an Elemental document. When rendering a message, this node is turned into output only for the email channel; for other channels it produ…
2 properties 1 required
ElementalImageNode
object
Used to embed an image into the notification.
5 properties 1 required
NotificationContent
VersionNode
object
A version entry for a notification template.
4 properties 3 required
BaseError
object
1 property 1 required
Notification
object
9 properties 6 required
NotificationChannel
object
5 properties 1 required
SubmissionChecksGetResponse
object
1 property 1 required
Paging
object
2 properties 1 required
NotificationLocalePutRequest
object
Request body for setting locale-specific content overrides. Each element override must include the target element ID.
2 properties 1 required
MessageRoutingChannel
NotificationChannelContent
object
2 properties
TextAlign
string
ElementalMetaNode
object
The meta element contains information describing the notification that may be used by a particular channel or provider. One important field is the title field…
1 property
NotificationTemplatePublishRequest
object
Optional request body for publishing a notification template. Omit or send an empty object to publish the current draft.
1 property
NotificationTemplateVersionListResponse
object
2 properties 2 required
NotificationTemplateResponse
Response for GET /notifications/{id}, POST /notifications, and PUT /notifications/{id}. Returns all template fields at the top level.
TextStyle
string
ElementalDividerNode
object
Renders a dividing line between elements.
1 property
IAlignment
string
NotificationContentHierarchy
object
2 properties
NotificationTemplateState
string
Template state. Defaults to DRAFT.
NotificationElementPutRequest
object
Request body for updating a single element. Additional type-specific fields are allowed.
7 properties 1 required
ElementalQuoteNode
object
Renders a quote block.
5 properties 3 required
Locale
object
1 property 1 required
ElementalActionNode
object
Allows the user to execute an action. Can be a button or a link.
7 properties 3 required
NotFound
object
1 property 1 required
NotificationTagData
object
2 properties 2 required
MessageRoutingMethod
string
IActionButtonStyle
string
Locales
objectnull
BlockType
string
NotificationTemplateCreateRequest
object
Request body for creating a notification template.
2 properties 1 required
NotificationContentMutationResponse
object
Shared mutation response for PUT content, PUT element, and PUT locale operations. Contains the template ID, content version, per-element checksums, and resulti…
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

courier-notification-templates-api-openapi.yml Raw ↑

Other APIs Courier publishes across the network.

Courier Inbox Real-Time API
AE Profile APIs.io
Courier Audiences API
AE Profile APIs.io
Courier Audit Events API
AE Profile APIs.io
Courier Authentication API
AE Profile APIs.io
Courier Automations API
AE Profile APIs.io
Courier Brands API
AE Profile APIs.io
Courier Bulk API
AE Profile APIs.io
Courier Courier Create API
AE Profile APIs.io
Courier Device Tokens API
AE Profile APIs.io
Courier Inbound API
AE Profile APIs.io
Courier Journeys API
AE Profile APIs.io
Courier Lists API
AE Profile APIs.io
#Notification Templates
← Back to C APIs
API Details
ID
courier:courier-notification-templates-api
Base URL
https://api.courier.com
Docs
https://www.courier.com/docs/reference
Provider
Courier
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=courier-notification-templates-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/courier-notification-templates-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Courier Notification Templates API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.