LIke this
https://developers.facebook.com/docs/messenger-platform/send-messages/template/button
https://developers.facebook.com/docs/messenger-platform/send-messages/buttons
https://developers.facebook.com/docs/messenger-platform/send-messages/quick-replies

https://developers.facebook.com/docs/messenger-platform/reference/messenger-profile-api/domain-whitelisting/

there will be a breaking change rolling out, message type
please add this attribute when sending messages.

Facebook provides a header which can be used to find the SHA256 checksum of a communication. We should use this to ensure the integrity of our messages. I don't anticipate this being complex to implement.

https://developers.facebook.com/docs/messenger-platform/webhook-reference#security

hi, struct MessageInfo miss game_play in receiving.go, and I cannot reveive messaging_game_plays Webhook Event.

According to the messenger docs, the default fields have changed and to access the other fields, one has to ask for access.

From my usage of other bots building libraries/software and also bare development without one, this will throw permission error and we'd have to change the default fields.

I am working on a simple PR to change these --the default fields.

I think it should be relatively easy to get some basic tests going, however it looks like it will be a pain to get any full blown integration tests happening.

One of the cool features of the Facebook Messenger Platform is that it is possible to send "structured messages" like the following:

Currently we do not provide access to this section of the API. Obviously this functionality would be built into the Response structure.

I'm not quite sure what it would look like at the moment, but a start would be just to mirror to JSON structures for everything:

{
  "recipient":{
    "id":"USER_ID"
  },
  "message":{
    "attachment":{
      "type":"template",
      "payload":{
        "template_type":"button",
        "text":"What do you want to do next?",
        "buttons":[
          {
            "type":"web_url",
            "url":"https://petersapparel.parseapp.com",
            "title":"Show Website"
          },
          {
            "type":"postback",
            "title":"Start Chatting",
            "payload":"USER_DEFINED_PAYLOAD"
          }
        ]
      }
    }
  }
}

Then eventually we could add some sort of "API sugar", like Response.AddButton, Response.AddElement, etc.

Ability to reuse attachments in messages with attachment API:

https://developers.facebook.com/docs/messenger-platform/reference/attachment-upload-api/#attachment_reuse

At the moment it is impossible to send a message to a user out of the blue without some voodoo.

I'd suggest adding a Send(r Recipient, m string, replies []QuickReply) function onto the Messenger struct.

Hello,

First thanks ! I love the project !

How to set the in_test value to true ?

Needed for Extensions, see: https://developers.facebook.com/docs/messenger-platform/reference/messenger-profile-api/home-url

Could you provide an extensions example made with this library ? (if not, i will once i did it ;) )

Hey there,

With some functions, like CallToActionsSetting sometimes Facebook rejects it, but no error is returned by the function. So I'm thinking of adding a debug mode to your package, would that be suitable to you ?
For example, simply by outputting the result of the request, I was able to see that I was doing something wrong :
{"error":{"message":"(#105) Number of call to actions exceeds the maximum allowed number"...}

Or maybe parse the response and check for that error field ?

I think it is a good idea to allow people to use a config file. This allows separation of concern and you can be guaranteed that the configurations are in a separate file and can be changed at will.

Makes good for better dev experience. I have a PR for this 🙃

I don't know if they were numbers before, but at least now, user IDs from webhooks are numbers in strings. i.e. the json would be like:

{"sender":{"id":"1259905410705036"},"recipient":{"id":"1175644529126109"}, "..." }

This can be fixed by changing the structs to use strings instead of int64, or use something during decoding to convert it to an int64.

Looking at our mod file, we currently depend on testify/assert (and then it depends on another library) -- it seems we only actually use testify for some deep-equal checks in messenger_test.go.

I'd prefer it if we just wrote our own functions for this behavior in order to eliminate any dependencies we don't actually need.

Is it possible, if so - how to handle multiple pages with the same endpoint?

Something like Chatfuel? When you connect your page and bot serves that page.

Dump way:

for i := 0; i < n; i++ {
   client := messenger.New(...)
   http.Handle("/messenger", client.Handler())
}

This throws error that "/messenger" already registered. Is there a smarter way to this?

https://developers.facebook.com/docs/messenger-platform/guides/chat-extensions

Reference: https://developers.facebook.com/docs/graph-api/reference/user

I think we are missing implementation of Get Started button and Persist Menu setting.
I'm setting it by extending your package, but who knows if this will be added to the framework?