Skip to main content
PUT
Update an email template

Authorizations

x-APIKey
string
header
required

The authentication system on Partoo API is using API Key that should be put in the header of the request (the name of the header is x-APIKey). An api_key is linked to a user. This user's role will give you different access level to the API features.

Path Parameters

template_id
number
required

Template id

Body

application/json
name
string

Internal name for the template

Example:

"Default Template"

subject
string

Email subject line

Example:

"We'd love your feedback"

title
string

Title displayed in the email body

Example:

"How did we do?"

body
string

Main body text of the email

Example:

"Thank you for visiting us. Please take a moment to share your experience."

cta_text
string | null

Call-to-action label. Required when cta_type is BUTTON.

Example:

"Leave a review"

cta_type
enum<string>

Type of call-to-action rendered in the email.

  • BUTTON: a clickable button; cta_text must be non-null.
  • EMBEDDED_NPS: an NPS score row embedded in the email.
Available options:
BUTTON,
EMBEDDED_NPS
Example:

"BUTTON"

post_cta_text
string | null

Text displayed below the call-to-action

Example:

"Your feedback helps us improve."

closing_text
string | null

Closing paragraph of the email

Example:

"Thank you for your time!"

signature_name
string | null

Name displayed in the email signature

Example:

"The Partoo Team"

logo_url
string<uri> | null

URL of the organization logo displayed in the email header

Example:

"https://example.com/logo.png"

banner_url
string<uri> | null

URL of the banner image displayed in the email

Example:

"https://example.com/banner.png"

color
string

Primary accent color for the email template (hex code)

Example:

"#3B82F6"

font_family
enum<string>

Font family used in the email

Available options:
Arial,
Helvetica,
Verdana,
Georgia,
Trebuchet
Example:

"Arial"

Response

OK

name
string
required

Internal name for the template

Example:

"Default Template"

subject
string
required

Email subject line

Example:

"We'd love your feedback"

title
string
required

Title displayed in the email body

Example:

"How did we do?"

body
string
required

Main body text of the email

Example:

"Thank you for visiting us. Please take a moment to share your experience."

cta_type
enum<string>
required

Type of call-to-action rendered in the email.

  • BUTTON: a clickable button; cta_text must be non-null.
  • EMBEDDED_NPS: an NPS score row embedded in the email.
Available options:
BUTTON,
EMBEDDED_NPS
Example:

"BUTTON"

color
string
required

Primary accent color for the email template (hex code)

Example:

"#3B82F6"

font_family
enum<string>
required

Font family used in the email

Available options:
Arial,
Helvetica,
Verdana,
Georgia,
Trebuchet
Example:

"Arial"

id
integer
required

Unique identifier of the email template

Example:

1

org_id
integer
required

The organization ID that owns this template

Example:

42

created_at
string<date-time>
required

Date and time the template was created

Example:

"2024-01-15T10:30:00+00:00"

updated_at
string<date-time>
required

Date and time the template was last updated

Example:

"2024-06-01T08:00:00+00:00"

cta_text
string | null

Call-to-action label. Required when cta_type is BUTTON.

Example:

"Leave a review"

post_cta_text
string | null

Text displayed below the call-to-action

Example:

"Your feedback helps us improve."

closing_text
string | null

Closing paragraph of the email

Example:

"Thank you for your time!"

signature_name
string | null

Name displayed in the email signature

Example:

"The Partoo Team"

logo_url
string<uri> | null

URL of the organization logo displayed in the email header

Example:

"https://example.com/logo.png"

banner_url
string<uri> | null

URL of the banner image displayed in the email

Example:

"https://example.com/banner.png"