https://reply.io logo
#feedback
Potential Bug with `emailTemplateId` . API returns a 400 demanding `subject`…
# feedback
m

Max Foster

05/03/2026, 7:41 PM
Potential Bug with
emailTemplateId
. API returns a 400 demanding
subject
and
message
- even though according to the new API docs both should be ignored when
emailTemplateId
is provided. We have a customer trying to create email sequence steps with PDF attachments via API V3. The expected workflow based on the docs is: • upload attachment • create email template with that attachment • create a sequence step referencing the template via
variants.emailTemplateId
. The issue:
emailTemplateId
does not work. When provided, the API returns a 400 demanding
subject
and
message
Based on my tests. when those are provided - the step is created with the content of the
subject
and `message`completely ignoring the template and skipping the attachment.
Copy code
POST /v3/sequences/1678728/steps

{
  "type": "Email",
  "delayInMinutes": 0,
  "executionMode": "Automatic",
  "variants": [{ "emailTemplateId": 242978 }]
}
Copy code
{
  "status": 400,
  "title": "Validation failed",
  "detail": "The request body contains validation errors.",
  "extensions": {
    "errors": [
      "Email template message is required.",
      "Email template subject is required."
    ]
  }
}
The workaround with using the emailTemplateId with the V2 calls (Create Campaign (Template Step Text) and Add Step to Campaign) seems to be working as expected and Steps are created with the template content and attachments.
👀 1