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

Courier Courier Create API

The Courier Create API from Courier — 4 operation(s) for courier create.

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

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

This API exposes 5 operations across 4 paths, and defines 45 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.

5 operations 4 paths 45 schemas 3 GET1 POST1 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 Courier Create API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Courier Create 5
GET
/tenants/{tenant_id}/templates/{template_id}
Get a Template in Tenant
tenants_getTemplateByTenant 2 params → 200400
PUT
/tenants/{tenant_id}/templates/{template_id}
Create or Update a Tenant Template
tenants_replaceTemplate 2 params body → 200201400404413
POST
/tenants/{tenant_id}/templates/{template_id}/publish
Publish a Tenant Template
tenants_publishTemplate 2 params body → 200400404
GET
/tenants/{tenant_id}/templates/{template_id}/versions/{version}
Get a Specific Template Version
tenants_getTemplateVersion 3 params → 200400404
GET
/tenants/{tenant_id}/templates
List Templates in Tenant
tenants_getTemplateListByTenant 3 params → 200400

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are ElementalTextNode (10 properties), Channel (7 properties), ElementalActionNode (7 properties), ListTemplatesByTenantResponse (6 properties). Each schema is shown below with its type and property counts.

MessageChannels
object
ElementalNode
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
ChannelMetadata
object
1 property
PostTenantTemplatePublishResponse
object
Response from publishing a tenant template
3 properties 3 required
TenantTemplateData
object
The template's data containing it's routing configs and Elemental content
2 properties 2 required
MessageProviders
object
ListTemplatesByTenantResponse
object
6 properties 3 required
BadRequest
object
1 property 1 required
MessageRouting
object
2 properties 2 required
TenantTemplateInput
object
Template configuration for creating or updating a tenant notification template
4 properties 1 required
ElementalBaseNode
object
4 properties
MessageProvidersType
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
TenantTemplateDataNoContent
object
The template's data containing it's routing configs
1 property 1 required
BaseTemplateTenantAssociation
object
5 properties 5 required
ElementalImageNode
object
Used to embed an image into the notification.
5 properties 1 required
BaseError
object
1 property 1 required
MessageRoutingChannel
SingleTemplateTenantAssociation
object
1 property 1 required
PutTenantTemplateRequest
object
Request body for creating or updating a tenant notification template
2 properties 1 required
TextAlign
string
UTM
object
5 properties
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
PayloadTooLarge
object
Error returned when the request payload exceeds the maximum allowed size
1 property 1 required
Metadata
object
1 property
TextStyle
string
ElementalDividerNode
object
Renders a dividing line between elements.
1 property
IAlignment
string
Timeouts
object
2 properties
RoutingMethod
string
ElementalQuoteNode
object
Renders a quote block.
5 properties 3 required
Locale
object
1 property 1 required
Channel
object
7 properties
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
ListTemplateTenantAssociation
object
1 property 1 required
MessageRoutingMethod
string
GetTemplateByTenantResponse
object
Locales
objectnull
PutTenantTemplateResponse
object
Response from creating or updating a tenant notification template
3 properties 2 required
IActionButtonStyle
string
PostTenantTemplatePublishRequest
object
Request body for publishing a tenant template version
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

courier-courier-create-api-openapi.yml Raw ↑

Other APIs Courier publishes across the network.

Courier Inbox Real-Time API
Courier Audiences API
Courier Audit Events API
Courier Authentication API
Courier Automations API
Courier Brands API
Courier Bulk API
Courier Device Tokens API
Courier Inbound API
Courier Journeys API
Courier Lists API
Courier Notification Templates API
Where this information came from

This is an independent, third-party profile of Courier Courier Create 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.