{"id":49,"date":"2021-05-17T10:53:39","date_gmt":"2021-05-17T02:53:39","guid":{"rendered":"https:\/\/kloudimp.com\/?p=49"},"modified":"2023-03-26T18:01:08","modified_gmt":"2023-03-26T10:01:08","slug":"facebook-chat-api","status":"publish","type":"post","link":"https:\/\/www.kloudimp.com\/facebook-chat-api\/","title":{"rendered":"Facebook Chat API"},"content":{"rendered":"\n
This is part of a series of \u201cBot Making Tools Assessment\u201d findings from the \u2018How To Build A Bot With The Right Kind Of Tools<\/a>\u2018 article.<\/p>\n\n\n\n Checkout the rest of the series by following these links:<\/p>\n\n\n\n The official Facebook Messenger Platform API<\/a> was launched on 25 March 2015 at F8 conference, and since then there has been a slew of online services catering to Facebook Messenger Bot Building<\/a>. All these online services connect to Facebook via the developer APIs (using REST protocol) and the development language of their developer\u2019s choosing. The documentation have improved a lot since version 1.0<\/a> . At time of writing, Messenger Platform API is version 2.1.<\/p>\n\n\n\n The approach Facebook is taking with bots is a lot more aggressive and driven as they have a much wider and diversified use case & user base compared to Skype at time of writing (no surprise here, technically they are also Social Media Platform, and \u201cnot just a messaging channel\u201d). Judging from the way Facebook is marketing their Messenger Platform and recent acquisitions in Artificial Intelligence related companies (they acquired Wit.ai and has integrated NLP features within the platform), this is a very interesting space to lookout for as they will also likely be the ones to introduce something new and developers can sign up for beta provided certain conditions are met.<\/p>\n\n\n\n If you live on the bleeding edge and love to play catch with the \u201clatest and greatest\u201d from Facebook, this is the way to go.<\/p>\n\n\n\n Be warned, these developer APIs are very granular and in no way \u201ca complete solution\u201d to bot building. The developer will need to plan and develop for \u201ceverything else\u201d (API monitoring, Database connectivity). The benefit of knowing the developer APIs well does pay off in the long run, especially when the platform is in the lead in the bot space.<\/p>\n\n\n\n A few caveats:<\/p>\n\n\n\n Suggested Use Cases:<\/p>\n\n\n\n Source:<\/p>\n\n\n\n\n
My Findings<\/h2>\n\n\n\n
\n
\n