Custom messages from CREATE API not reflected in the Admin Desiginer

​@Nanda90 - is there a reason you copied and pasted the text from this other thread on the Community?

• Call the forms/messages API and confirm your changes return correctly.

• Open the Designer’s Language tab—if it still shows defaults, that means it’s ignoring API edits.

• Try creating a minimal form via the API and push just one custom message to isolate if it’s form-specific.

I’ve hit this same wall before. When the form is created and updated via the API, the forms/messages endpoint will happily return your custom text, but the Admin Designer’s Language settings still show the defaults. The bigger problem is that once you make any edit in the Designer, the draft it creates doesn’t contain your API-set messages, so publishing wipes them back to default.

• What worked for me was narrowing down where the sync is breaking and ensuring the Designer is “aware” of the API changes before any draft is triggered.
• First, confirm the API call is succeeding: hit forms/messages directly and verify your custom values are in the response.
• Check the Designer’s Language tab before making any UI edits—if it’s showing defaults, it’s ignoring the API data in its draft state.
• As a test, create a small, new form via API, then push only a single message update. If the Designer picks this up, the issue might be tied to how the original form was first created.
• If your edits vanish after “Publish”, you may need to re-apply the messages via API right after publishing until Typeform updates how drafts pull message data.
• For tricky workflows, I sometimes keep a JSON backup of all custom messages so I can re-inject them instantly when they get reset by using a mod app from the appstore.