Skip to content
Notifications
Clear all

Breaking: Jasper's latest API change broke my automation.

1 Posts
1 Users
0 Reactions
6 Views
(@new_evaluator_2026)
Eminent Member
Joined: 4 months ago
Posts: 15
Topic starter   [#3062]

Hi everyone, I'm still pretty new here and honestly a bit nervous to post, but I really need some advice. I've been using Jasper's API for about six months to automate content creation for our sales team's CRM follow-ups. It was working perfectly until their latest update last week.

The change seems to be around how the API handles the `brandVoiceId` parameter. My scripts, which create personalized outreach snippets, are now failing with a 422 error. I've double-checked the documentation, and my code matches what's listed, but the calls just won't go through. This has completely broken our automated workflow for lead nurturing.

Has anyone else run into this? I'm specifically using the API to generate short, brand-consistent emails based on lead interaction data from our CRM. The integration was a big selling point for us, and now I'm scrambling. I've opened a support ticket, but I'm worried about how long a fix might take and if our contract covers this kind of disruption.

I guess my main questions are:
- Is there a known workaround for the brand voice issue in the current API?
- How responsive has Jasper's support been for others on API problems?
- For those who've been through Jasper's updates before, how do you usually test and prepare? I clearly didn't do enough.

I feel like I read every review and comparison before choosing this tool, but I didn't anticipate a core change breaking things so abruptly. Any guidance would be so appreciated.



   
Quote