Skip to content
A JavaScript API for creating Facebook Messenger bots in node
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


A Node.js client for the Facebook Messenger Platform. The API is largely influenced by messenger-bot.


npm install git+


// express (or any connect-compatible app)
const app = require("express")()
const bodyParser = require("body-parser")

// sprine bot
const Bot = require("sprine").Bot
const send = require("sprine").send  //- module for Sender API

let bot = new Bot({
    token: "PAGE_TOKEN",

/** subscribe to bot events */

//- error
bot.on("error", err => console.error(err))

//- message
bot.on("message", (event, reply) => {
    // event is an instance of FacebookEvent
    console.log("[%s]: %s", event.sender, event.timestamp)

    // send an image attachment
    let msg0 = new send.Message(
                new send.ImageAttachment("")

    // send quick reply template
    let msg1 = new send.Message(
                "Red or Blue?",
                [send.QuickReply.text("Red", "COLOR_RED"),
                 send.QuickReply.text("Blue", "COLOR_BLUE")]

    // ask for location
    let msg2 = new send.Message(
                "Weather! but for where?",

    //- Reply to the message

    // 1. Simple text
    reply("Hello there! I got your message")

    // 2. Composed Message
    reply(msg1) // or msg2, msg3, etc.

    // 3. Or a complete Payload
    let payload = new send.Payload(
            new send.Recipient(event.sender),
            null, // sender actions
            send.Notification.SILENT  // notification type

    reply(payload).then(resp => console.log(resp)

// use a middleware to parse post data. This is required from the application side.

// add a middleare to your app to handle Messenger webhook calls
app.use("/facebook", bot.middleware())

// run

Note: The application must provide a connect-compatible middleware to parse POST data or else the bot will raise an exception about missing data argument when a message is received.


class Bot extends EventEmitter

The base class the user mainly interacts with. This class provides functions and events that helps the user tap into events and messages received from Facebook and respond to them.

let bot = new Bot(options)

Returns a new Bot instance

options - Object

  • token {string} - Your Page Access Token. Required.
  • verify {string} - Verification token for one-time setup. Required, if you want the bot to handle verification for you.
  • subscribe {boolean} - Subscribe App to the Page on initialization. Optional.


Returns a connect-compatible middleware function.

Bot#sendMessage(to, data [, callback])

Send a message data to target to. Returns a promise. Also see Facebook Send API

  • to {string} - Page-scoped ID of the intended recipient. Required, if data is not an instance of Payload. If data is an instance of Payload then this is ignored.
  • data {string|Message|Payload} - The message to send. Can be a string/text, a Message or a Payload. Required.


The message processing routine. Either invoke this routine with the data received from Facebook or use the middleware which invokes it internally. This routine parses the message and trigger events for each kind of message received.

  • data {object} - Data received from Facebook. Required.

Bot#handleVerification(request, response)

Handle webhook validation request.

  • request - A connect-compatible request object.
  • response - A connect-compatible response object.


Subscribes the App to Page programmatically. Returns a promise.

Bot#getProfile(id [, callback])

Get the User's Profile. Returns a promise which resolves either to a User Profile object or an empty object depending on whether the profile is available or not.

  • id {string} - Page-scoped ID of the user. Required. Usually, this is the event.sender property of the concerned message.

Bot#setField(field, payload [, callback])

Sets a field for the Messenger Profile API

  • field {string} - Name of the field. Required.
  • payload {object} - Object payload to set. Required.

Bot#deleteField(field [, callback])

Deletes a field for the Messenger Profile API

  • field {string}: Name of the field to delete


Shorthand function to enable the Get Started Button


Shorthand function to disable the Get Started Button


Every event, except the error event, receives a FacebookEvent object and a reply(data [, callback]) function that's an alias to Bot#sendMessage(to, data [, callback]) with a bound ID.

List of events:

  1. message: fired when a message is received.
  2. echo: fired when an echo is received.
  3. postback: fired when a postback is received.
  4. delivery: fired when a delivery receipt is received.
  5. read: Fired when a read receipt is received.
  6. authentication: Fired when an optin is received.
  7. referral: Fired when a referral is received.
  8. account-linked: Fired when an Account Linking event with status linked is received.
  9. account-unlinked: Fired when an Account Linking event with status unlinked is received.
  10. unknown: Fired when an unknown event is received.
class FacebookEvent

The FacebookEvent class. The instance of this class is passed to the event listeners when an event is received.


A getter-property to access the event's sender id.


A getter-property to access the event's timestamp.


A getter-property to get the event's type.


A getter-property to get the data object associated with the event. The shape of this object depends on the type of event, see Webhook Reference for more details.

Send API

For a reference to Send API, check the documentation here


  • Add classes to wrap message data recieved from Facebook and provide easy interface to work with that
  • Add custom callback for specific types of Postback payloads. For eg., we can have a QuickReply with a payload field set to SOME_PAYLOAD, then we can listen for that specific Postback by having something like, bot.on('postback:SOME_PAYLOAD', (event, reply) => {...})
  • Add tests
  • (Low Priority) Add some generic session/context management support within the bot itself. The argument for this is that some of us would be using this library alongwith other AI-services (like for which we may want to add some kinda session support to our bot

PR for adding above mentioned features are welcomed! For other feature request or for reporting bugs use Github Issues.

You can’t perform that action at this time.