Chatbot Templates still contains subHeader -> API call fails

#1

In these documents, the subHead attribute is still described:

(see curl example)

If you post with a subtitle, you receive the weird answer that your message is not a valid json:

{"message":"Request content should be a valid JSON object/string","code":7001}

Without the subHead, the post works as expected. Please review the docs.

0 Likes

#2

Hi @Bernd_Gewehr,

Thanks for pointing that out. We have corrected the JSON within the content to work in our docs.

0 Likes

#3

I suggest to delete this page completely:

and link to the chat bot cookbook here instead:

1 Like

#4

Hi @Bernd_Gewehr,

Thanks for your input, it makes sensed to consolidate the chatbot template pages. We’ll update it accordingly.

Thanks

0 Likes

#5

Good choice to move that information to the chatbot cookbook.

Sorry to insist on it, but this page needs some corrections:

  • remove subhead from basic template
  • explain that the lower examples only ADD to the body payload
  • correct the drop selection image
  • fill the drop selections schema
  • correct the editable event to sendHttpMsg

Sorry but the quality of this page is horrible.

0 Likes

#6

Thanks @Bernd_Gewehr, will update the details on this page soon.

0 Likes

#7

When is soon? :grinning:

0 Likes

#8

Still that page is available with all its errors…

Please care!

0 Likes

#9

Hi @Bernd_Gewehr,

Thank you for your patience, we’ve updated the templates to remove the errors. Please let us know if they are working for you.

Thanks

0 Likes

#10

Excuse me if I‘m wrong @Michael_Purnell but as long as there is a subheader on that page - it’s not corrected. Didn’t recheck the other issues.

0 Likes

#11

Hi @Bernd_Gewehr,

The sub headers have been removed along with the dropdown templates due to it not being supported right now.

Thanks

0 Likes

#12

These subheaders seem to be very sticky:

0 Likes

#13

@Bernd_Gewehr Might be a caching issue, we republished the docs just in case if its something on our end. Try refreshing again.

Thanks

0 Likes

#14

Solved. Thank you!!!

0 Likes