Integration

In this section you will find a series of more advanced functionalities that require a more complex development. We recommend that a developer be in charge of this configuration.

Below we indicate the models of the objects that are used:

Inbox = {
    lastAccess: "string",
    count: "int",
    pageSize: "int",
    numPage: "int",
    notifications: [InboxNotifications],
    newNotifications: [InboxNotifications]
}

InboxNotifications = {
    id: "string",
    sentAt: "string",
    status: "String",
    sendingId: "int",
    campaignId: "string",
    message: Push
}

InboxCounter = {
    click: "int",
    sent: "int",
    deleted: "int",
    unread:{
        lastAccess: "string",
        count: "int"
    }

}

User identification

In order to get the notifications from Indigitall's Inbox, the user must identify himself. First you have to initialize the SDK of Indigitall so that it generates our identifier (deviceId) and be able to associate it to the custom ID that you associate to the device.

To perform the registration tasks, these two methods are used:

//User ID
tiindigitall.logIn("YOUR_ID",(device)=>{
  //DO SOMETHING  
}, (error)=>{
  //LOG ERROR 
});

tiindigitall.logOut(device=>{
  //DO SOMETHING  
}, (error)=>{
  //LOG ERROR 
});

Generate authentication token

In this section you will see how to generate a validation token for an application that has configured authentication with webhook. To generate this token, you need to add the JSON with the configuration on method calls explain on Initialization section.