API documentation

Login username (email address)

Login password

The type of channels accessed by the logged in user. Possible values are cs for customer-service channels, and nl for newsletter channels. Leave empty for listing all channels.

A code generated for new agents or when restoring a forgotten password. If the code matches, the specified password is used from now on for the agent. Or a code sent for 2-factor authentication.

Token with login data

Channel ID for activating this channel

The whatsapp number to which the 2fa code will be sent, cannot be overwritten

Login username (email address)

The user ID, number or secret hash code. Multiple ids can be separated by comma.

This is the amount of results that is returned.

Active and inactive users are listed per default. Use 1 for listing only active users and 0 for listing only inactive users.

This is the amount of results skipped in the result set.

Set to 1 for listing only blocked users

List only active users of this targeting group.

Users can be searched by id/phone number (if the search attribute is numeric) or by parts of their name or referral info.

User lists are ordered by creation date per default. stopped, id, name, messenger, blocked or last_chat can be specified to order by those attributes.

Normally user lists are sorted descending which means latest first.

Set if the time of the last user chat should be included.
Retrieving the information costs more time.

Set if custom fields should be included.

A JSON array of user filter. If multiple filters are specified, all are applied. Each filter element can have the following elements:

• type: mandatory type of the filter. Possible value is created or customfield
• after: UNIX timestamp of created or last update of a customfield
• before: UNIX timestamp of created or last update of a customfield
• name: name of a custom field (default all)
• value: Value of a custom field

Only list users who have latest been chatting with the chatbot without having a ticket

Possible values json or csv. Only applies for listing users.

The user ID, number or secret hash code. Multiple ids can be separated by comma.

Requires JSON with field name => field value.
Possible field names:

• name: name of the user
• agent: email-address of an agent that should be assigned
• customfields: Please see possible user properties by using the GET USER PROPERTIES call.
  Example:

  {  
  "name": "John Doe",  
  "agent": "john.doe@foo.bar",  
  "customfields": {  
  "haircolor": "brown",  
  "123": "premium"  
  },  
  "addlabel": [1,2,3],  
  "removelabel": [4,5,6]  
  }  

The CSV file containing the user list.
Only fields provided within the file will be handled
The following fields are possible:

• Regular fields:
  • id
    mandatory
    Id of the contact, differs by messengers, for WhatsApp for example this would be a phone number
  • messenger
    mandatory
    Identifier for the contacts messenger. Possible values: CC for Custom Messenger, FB for Facebook, IM for IMessage, TG for Telegram, VI for Viber, WB for WhatsApp, WN for Notify
  • name
    Username of the contact
• Control fields:
  • activated
    1: user should be activated for mia, 0: user should be deactivated for mia
  • blocked
    1: user should be blocked, 0: user should be unblocked
  • deactivated
    1: user should be deactivated for mia, 0: user should be activated for mia
  • deleted:
    1: user should be deleted, 0: user should not be deleted
• Every user property which is set up for your channel, by the name of the property

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The category ID.

Set active (1) or inactive (0).

A comma-separated list of user numbers. Leave empty to list all users with the property.

The name of the user property

The user number. Multiple numbers can be separated by comma.

The name of the user property

The value of the user property. Must be compliant with the possible field values.

The field ID or name

Set to 1 if hidden fields should be included.

The name of the user property, no spaces. "fieldname" will result in a bot variable $fieldname$.

Possible field types:

• number
• text
• word
• enum
• collection
• location
• date
• time

Possible values or conditions for this field.
e.g. >=2 <=9 for field type number.
a,b,c,d for field type enumeration or collection

Expiration in seconds

• 0: won't be saved and can only be used in the answer associated with the input
• >0: Seconds before information will be purged
• -1: permanent

Field can be edited on the "profile page" by the user.

Internal name for the variable (also shown on users profile page)

The position of the field. Per default it is added at the end.

Field is only visible with appropriate rights (not for normal agents).

Default value that is replaced if no value is stored in the user profile.

The field ID or name

The name of the user property, no spaces. "fieldname" will result in a bot variable $fieldname$.

Possible field types:

• number
• text
• word
• enum
• collection
• location
• date
• time

Possible values or conditions for this field.
e.g. >=2 <=9 for field type number.
a,b,c,d for field type enumeration or collection

Expiration in seconds

• 0: won't be saved and can only be used in the answer associated with the input
• >0: Seconds before information will be purged
• -1: permanent

Field can be edited on the "profile page" by the user.

Internal name for the variable (also shown on users profile page)

The position of the field.

Field is only visible with appropriate rights (not for normal agents).

Default value that is replaced if no value is stored in the user profile.

The field ID or name

The user ID, number or secret hash code. Multiple ids can be separated by comma.

This is the amount of results that is returned.

Show start and stop messages from users.

The user ID, number or secret hash code. Multiple IDs can be separated by comma. The user number / id must be numeric only. Do not add a "+" to the user number (WhatsApp)

The text message to be send to the user. Sending an attachment with a message is only possible for image and video. Audio and document will ignore the message.

The url of the attachment. The following types/extensions are supported: image (jpg, jpeg, png, gif), video (mp4, m4v, mpg, mpeg, mov, avi), audio (mp3) or document (pdf). If the attachment is valid, a field called reusable_attachment is in the result, containing a cached URL for the sent file. Use this URL the next time for sending the same file to other users to improve the performance.

The filename of the attachment. It can be displayed in messengers that don't support inline view of the attachment.

If set, mark the chat with this user as read (1) / unread (0).

Buttons can be attached for all messengers except WhatsApp. A JSON encoded array of buttons can be passed. Each button must define a caption (displayed text), a type (link, postback, call or share) and an info field.

• Link must contain a URL.
• Postback a text send back to the server when the user clicks on it
• Call a phone number
• Share a link that can be shared (Facebook only)
  Example:

  [  
  {"type":"link", "caption":"MessengerPeople", "info":"https:\/\/www.messengerpeople.com"},  
  {"type":"postback", "caption":"Hello","info":"Hello"}  
  ]  

The parameter "meta" can contain any key => value pairs, that do not use reserved names. Mainly used for internal purposes

Array or comma-separated list of user numbers for sending to a larger number of users. Use instead of the id parameter. Performance-optimized so it does not update tickets of individual users. Just a list of success and failure numbers is returned.

Optional filter to use for sending in batch mode. Valid filters are all parameters given in endpoint USER GET.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The name of the notification

A JSON array of parameters that are replaced in the notification

ISO 639-1 Language Code of the notification, that should be send. Defaults to the channel language if no default language for the notification template is set. Mandatory if parameter notification is set

Array or comma-separated list of user numbers for sending to a larger number of users. Use instead of the id parameter. Performance-optimized so it does not update tickets of individual users. Just a list of success and failure numbers is returned.

Optional filter to use for sending in batch mode. Valid filters are all parameters given in endpoint USER GET.

The name of the notification template

A JSON array of parameters that are replaced in the notification.
For example: ["$profile_name$", "Value 2"]

The url of the header attachment. The following types/extensions are supported: image (jpg, png), video (mp4) or document (pdf). If the attachment is valid, a field called reusable_attachment is in the result, containing a cached URL for the sent file. Use this URL the next time for sending the same file to other users to improve the performance.

The text to be placed into the header variable

The suffix added to a dynamic link button

Language Code of the notification, that should be send.
Defaults to the channel language if no default language for the notification template is set.
Mandatory if parameter notification_template is set.
All available Language Codes can be found on the page https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates.

The user ID, number or secret hash code. Multiple IDs can be separated by comma.

The ID of the topic

The ID of the chat

JSON with field name => field valuepairs which will be set as user properties before sending. see possible user properties by using the GET USER PROPERTIES call.
Example: { "color": "red" }

The id of the chat that should be deleted

New name of the channel

Status message of the channel

Welcome message for new users

Ticket message for existing users

Set if a read confirmation should be sent in WhatsApp when receving chat messages

Set to enable the linkpreview-feature in WhatsApp and Telegram

Set to interpret every word as "Start" message. When disabled, only the default start word in the channels language or the specific start word is active.

When startword is set and every_word_starts is set to 0, users are only activated if they send this specific word

The timezone, e.g. "Europe/Berlin" or "America/Los_Angeles"

The amount of days after which inactive users are deleted automatically

Default language for this channel. Possible languages:
de, en, d1 (formal German), es, fr, it, nl, pl, pt, ru, r1, ar, tr, hr and jp

URL of the profile image of the channel

Time in minutes after which a ticket is marked as "overdue"

Time in minutes after which a ticket is marked as "critical"

Set if you want to open a ticket even if the chatbot answered already.

Time in minutes after which a ticket is reopened after it has been closed. Default 60

Time in minutes after which a ticket is closed automatically. Default 0

Set if you want to use autorouting of tickets.

Set if you want to assign tickets to agents automatically.

Set if you want to assign a ticket automatically to a previously assigned agent.

Set to 2 for automatically deactivating a bot when the agent sends a chat response or to 1 when a ticket is opened.

Any information in json format used by a frontend to store channel specific settings

The maximum number of tickets that are assigned to an agent by auto routing.

Set if you want to assign a ticket automatically only to online agents.

Set if you want to activate auto routing by keywords

Configuration for apple payment in json format

Set if you want to enable urltracking with shortened URLs. Contact MessengerPeople if you want to use your own domain instead of www.msgp.pl.

Parameters that are added to linked URLs if a user clicks on the link. %SOURCE% will be replaced by the used messenger

Set if you want to add the categories info to the welcome message.

The categories info that can be added to the welcome message. %LINK% will be replaced by a user specific link

Specifies whether notifications are used when sending content.

The number of unread information messages a user gets when requesting informations.

The maximum age in seconds of unread information messages a user gets when requesting informations.

An array of default texts that can be used when sending information

The message that a user gets when he tries to pull content but got already all content.

The message that a user gets in Whatsapp in addition to a notification informing how to pull the content. {{1}} is replaced by the pull keyword.

The initial text that an iOS user will send after installing the Notify app.

The image displayed in the Notify app for the channel.

A short text describing your channel visible in the Notify app.

Specifies whether channel content can be displayed in the chat of Notify.

The status of the channel in the Notify app affecting the visibility in the categories list. Possible values are public, private or hidden.

Additional Notify promotion text to send only to WhatsApp users without the Notify app.

Welcome message for users subscribing for MIA content

Notify promotion text added to for WhatsApp users subscribing for MIA content

Goodbye message for users who are unsubscribing

Link to the privacy manifest

Specifies whether MIA content is pushed to messengers.

Specifies whether a reopened ticket should not be assigned to an agent. Default 0

The amount of days after which inactive Facebook users are stopped automatically

The amount of days after which inactive Notify users are stopped automatically

Specifies whether the bot menu should be used.

Specifies whether agents can delete single chat messages.

Specifies whether or not a note is mandatory on ticket close.

The days and hours when the webchat is available. Provide data in JSON format with a
comma-separated list of days as the key and a nested object with time-strings for from and to.
Default value is:

{"mon,tue,wed,thu,fri": {"from": "09:00", "to": "17:00"}}

This is the amount of results that is returned.

ID of the first result to be served

Show incoming messages.

Show outgoing messages.

Show automated / bot messages if bot = 1. If bot = 2 include also welcome and stop messages.

The name of the team

The ID of an agent that should be added to the team. Multiple IDs can be separated by comma.

The team ID. Multiple ids can be separated by comma.

The name of the team

The ID of an agent that should be added to the team. Multiple IDs can be separated by comma.

The ID of an agent that should be removed from the team. Multiple IDs can be separated by comma.

The team ID. Multiple IDs can be separated by comma.

The name of the label

The background color of the label in hex format, eg. BADA55

The text color of the label in hex format, eg. C0FFEE

The label ID. Multiple IDs can be separated by comma.

The name of the label

The background color of the label in hex format, eg. FACADE

The text color of the label in hex format, eg. BE1337

The label ID. Multiple IDs can be separated by comma.

Set if a confirm dialog should be displayed to new Facebook users

The text in the confirm dialog that new Facebook users are receiving.

Set if the Facebook "get started" button should be displayed to new users

The greeting message that Facebook users are receiving when sending the first message to the page.

The Facebook access token from an administrator connecting to a Facebook page.
For connecting the page the access_token, page_id and page_name must be set.
For disconnecting the page the access_token must be empty and page_id and page_name must be set.

The Facebook page ID

The Facebook page name

The URL of a webhook. All incoming messages will be pushed to this URL. It MUST return a JSON

{ "success": "true" }  

Otherwise the webhook will be deactivated after some failed attempts.

Set active (1) or inactive (0).

In case anything goes wrong, a notification will be sent to this email address.

Comma separated list of fields to be included in the webhook call.


Possible fields:

• id
• messenger
• usernumber
• date
• attachment
• attachment_type
• text
• welcome
• channelnumber
• userstatus
• chat_id
• bot_chatid
• is_retry

Default: "id,messenger,usernumber,date,attachment,attachment_type,text,welcome,channelnumber,userstatus,chat_id"

A test message is sent to the webhook to check whether everything works correctly.
The push contains three messages (2 x WhatsApp, 1 x Facebook) in one call:

{  
"messages":[ {  
"id":"62103206",  
"messenger":"WB",  
"usernumber":"4917212345678",  
"date":"1522938174",  
"attachment":"",  
"attachment_type":"",  
"text":"Usermessage 1",  
"welcome":"0",  
"channelnumber":"4915792312345",  
"userstatus":"1",  
"chat_id":"1234567",  
"bot_chatid":"12345",  
"is_retry":"1"  
},  
{  
"id":"62103207",  
"messenger":"WB",  
"usernumber":"4917212345678",  
"date":"1522938174",  
"attachment":"",  
"attachment_type":"",  
"text":"Usermessage 2",  
"welcome":"0",  
"channelnumber":"4915792312345",  
"userstatus":"1",  
"chat_id":"1234568",  
"bot_chatid":"12345",  
"is_retry":"0"  
},  
{  
"id":"62103295",  
"messenger":"FB",  
"usernumber":"998694828505",  
"date":"1522938208",  
"attachment":"",  
"attachment_type":"",  
"text":"message via facebook",  
"welcome":"0",  
"userstatus":"1",  
"chat_id":"1234569",  
"bot_chatid":"12345",  
"is_retry":"0"  
} ] }  

If the user is activated successfully by sending the chat, the field welcome has the value 1.
The field userstatus has the value -1, 0 or 1.

• -1: The user sending the chat was delete
• 0: The user sending the chat is inactive
• 1: The user sending the chat is active
  
  
  If the parameter webhook_fields is set, the test data will be adjusted according to the field list

This is the amount of results that is returned.

The ID of the newsletter that should be deleted. Only scheduled newsletter can be deleted when sending hasn't started yet.

The ID 1-10 of a category

The new name of the category. Maximum length of the name is 100 characters.

The name of the new category. Maximum length of the name is 100 characters.

The ID 1-10 of a category

The name of the template

Synchronize templates with WhatsApp before listing

The name of the template

The category of the template
Valid values: 'ACCOUNT_UPDATE', 'PAYMENT_UPDATE', 'PERSONAL_FINANCE_UPDATE', 'SHIPPING_UPDATE', 'RESERVATION_UPDATE', 'ISSUE_RESOLUTION', 'APPOINTMENT_UPDATE', 'TRANSPORTATION_UPDATE', 'TICKET_UPDATE', 'ALERT_UPDATE', 'AUTO_REPLY'

An array of translations with the following JSON structure. language and body_text are mandatory. Header parameter depend on the header type:

[  
"en_US": {  
  "language": "en_US",  
  "body_text": "Text of the notification with parameter {{1}}",  
  "header_type": "TEXT", <- one of TEXT, MEDIA  
  "header_text": "Header text with parameter {{1}}",  
  "header_media_type": "IMAGE", <- one of IMAGE, DOCUMENT, VIDEO, LOCATION  
  "footer_text": "Footer text",  
  "buttons": [ { <- up to 3 QUICK_REPLY buttons OR a URL and/or PHONE_NUMBER button  
    "type": "QUICK_REPLY", <- one of QUICK_REPLY, URL, PHONE_NUMBER  
    "text": "Button caption", <-  
    "url": "https://foo.com/{{1}}", <- only for type URL. Parameter is optional.  
    "phone_number": "0123456789", <- only for type PHONE_NUMBER  
  } ],  
  "sample": { <- sample data that helps WhatsApp in reviewing the template  
    "body_variables": [ <- one for each used body variable  
      "My variable 1",  
    ],  
    "header_media": "URL of media file",  
    "header_variable": "My header variable",  
    "button_variable": "Variable for dynamic URL button",  
  },  
}

In-App visibility of the template

The id of the template

The name of the template. Can only be changed if all translations are still in status DRAFT.

The category of the template
Valid values: 'ACCOUNT_UPDATE', 'PAYMENT_UPDATE', 'PERSONAL_FINANCE_UPDATE', 'SHIPPING_UPDATE', 'RESERVATION_UPDATE', 'ISSUE_RESOLUTION', 'APPOINTMENT_UPDATE', 'TRANSPORTATION_UPDATE', 'TICKET_UPDATE', 'ALERT_UPDATE', 'AUTO_REPLY'
Can only be changed if all translations are still in status DRAFT.

An array of translations with the following JSON structure. language and body_text are mandatory. Header parameter depend on the header type:

[  
"en_US": {  
  "id": 12345, <- ID of existing translation  
  "language": "en_US",  
  "body_text": "Text of the notification with parameter {{1}}",  
  "header_type": "TEXT", <- one of TEXT, MEDIA  
  "header_text": "Header text with parameter {{1}}",  
  "header_media_type": "IMAGE", <- one of IMAGE, DOCUMENT, VIDEO, LOCATION  
  "footer_text": "Footer text",  
  "buttons": [ { <- up to 3 QUICK_REPLY buttons OR a URL and/or PHONE_NUMBER button  
    "id": 12345, <- ID of existing button  
    "type": "QUICK_REPLY", <- one of QUICK_REPLY, URL, PHONE_NUMBER  
    "text": "Button caption", <-  
    "url": "https://foo.com/{{1}}", <- only for type URL. Parameter is optional.  
    "phone_number": "0123456789", <- only for type PHONE_NUMBER  
  } ],  
  "sample": { <- sample data that helps WhatsApp in reviewing the template  
    "body_variables": [ <- one for each used body variable  
      "My variable 1",  
    ],  
    "header_media": "URL of media file",  
    "header_variable": "My header variable",  
    "button_variable": "Variable for dynamic URL button",  
  },  
}]

In-App visibility of the template

The name of the template

The name of the template

The id of the template

The name of the template. Can only be changed if all translations are still in status DRAFT.

The category of the template
Valid values: 'ACCOUNT_UPDATE', 'PAYMENT_UPDATE', 'PERSONAL_FINANCE_UPDATE', 'SHIPPING_UPDATE', 'RESERVATION_UPDATE', 'ISSUE_RESOLUTION', 'APPOINTMENT_UPDATE', 'TRANSPORTATION_UPDATE', 'TICKET_UPDATE', 'ALERT_UPDATE', 'AUTO_REPLY'
Can only be changed if all translations are still in status DRAFT.

An array of translations with the following JSON structure. language and body_text are mandatory. Header parameter depend on the header type:

[  
"en_US": {  
  "id": 12345, <- ID of existing translation  
  "skip": true, <- skip this translation from review  
  "language": "en_US",  
  "body_text": "Text of the notification with parameter {{1}}",  
  "header_type": "TEXT", <- one of TEXT, MEDIA  
  "header_text": "Header text with parameter {{1}}",  
  "header_media_type": "IMAGE", <- one of IMAGE, DOCUMENT, VIDEO, LOCATION  
  "footer_text": "Footer text",  
  "buttons": [ { <- up to 3 QUICK_REPLY buttons OR a URL and/or PHONE_NUMBER button  
    "id": 12345, <- ID of existing button  
    "type": "QUICK_REPLY", <- one of QUICK_REPLY, URL, PHONE_NUMBER  
    "text": "Button caption", <-  
    "url": "https://foo.com/{{1}}", <- only for type URL. Parameter is optional.  
    "phone_number": "0123456789", <- only for type PHONE_NUMBER  
  } ],  
  "sample": { <- sample data that helps WhatsApp in reviewing the template  
    "body_variables": [ <- one for each used body variable  
      "My variable 1",  
    ],  
    "header_media": "URL of media file",  
    "header_variable": "My header variable",  
    "button_variable": "Variable for dynamic URL button",  
  },  
}]

In-App visibility of the template

The name of the template

The language of the translation

The name of the template

The language of the translation

The name of the template

The language of the translation

The ID of a single content.

List only drafts if filter = draft, scheduled if filter = scheduled or content that is already published if filter = published.

This is the amount of results that is returned.

This is the amount of results skipped in the result set.

Content lists are ordered by published date per default (creation date for drafts). created can be specified to order by this attributes.

Normally content lists are sorted descending which means latest first.

Specifies whether click statistics should be returned for URLs in contents. Requires enabled click tracking in the channel.
The result shows the total number of clicks and the number of clicks for each messenger.

Specifies whether reach statistics should be additionally split up in 'pulled from' and 'pushed to' for each messenger separately.

The text of the content. Content with audio or document media will ignore the text.

The url of a media attachment. The following types/extensions are supported: image (jpg, jpeg, png, gif), video (mp4, m4v, mpg, mpeg, mov, avi), audio (mp3) or document (pdf).

The original filename of the attachment.

If set, store the content as draft, otherwise it will be published.

The UNIX timestamp of the publication date in seconds (if not a draft). The current date is used per default.

A short text that is sent to inform the users about new content. This text is sent to the Notify app or to WhatsApp, if the user has no Notify app.

A special promotion text to be sent in a separate message with the content

If specified this link is opened directly from notifications in the Notify app. Other messengers will get the text + this weblink.

Buttons can be attached for all messengers except WhatsApp. A JSON encoded array of buttons can be passed. Each button must define a caption (displayed text), a type (link, postback, call or share) and an info field.

• Link must contain a URL.
• Postback a text send back to the server when the user clicks on it
• Call a phone number
• Share a link that can be shared (Facebook only)
  Example:

  [  
  {"type":"link", "caption":"MessengerPeople", "info":"https:\/\/www.messengerpeople.com"},  
  {"type":"postback", "caption":"Hello","info":"Hello"}  
  ]  

Category ID 1-10 or ID of a targeting list.

The lifetime of the content after publishing in seconds.

The id of the menu item holding the command that is used to pre-fill the users input field in WhatsApp in order to pull the content.

The name of the WhatsApp notification used for sending

A JSON array of parameters that are replaced in the WhatsApp notification

ISO 639-1 Language Code of the notification, that should be send. Defaults to the channel language if no default language for the notification template is set. Mandatory if parameter wb_notification is set

The name of the notification template

A JSON array of parameters that are replaced in the notification

The url of the header attachment. The following types/extensions are supported: image (jpg, png), video (mp4) or document (pdf). If the attachment is valid, a field called reusable_attachment is in the result, containing a cached URL for the sent file. Use this URL the next time for sending the same file to other users to improve the performance.

The text to be placed into the header variable

The suffix added to a dynamic link button

ISO 639-1 Language Code of the notification, that should be send. Defaults to the channel language if no default language for the notification template is set. Mandatory if parameter notification_template is set

The content ID

The text of the content. Content with audio or document media will ignore the text.

The url of a media attachment. The following types/extensions are supported: image (jpg, jpeg, png, gif), video (mp4, m4v, mpg, mpeg, mov, avi), audio (mp3) or document (pdf).

The original filename of the attachment.

If set, store the content as draft, otherwise it will be published.

The UNIX timestamp of the publication date in seconds (if not a draft). The current date is used per default.

A special notification text sent to the Notify app.

A special promotion text to be sent in a separate message with the content

If specified this link is opened directly from notifications in the Notify app. Other messengers will get the text + this weblink.

Buttons can be attached for all messengers except WhatsApp. A JSON encoded array of buttons can be passed. Each button must define a caption (displayed text), a type (link, postback, call or share) and an info field.

• Link must contain a URL.
• Postback a text send back to the server when the user clicks on it
• Call a phone number
• Share a link that can be shared (Facebook only)
  Example:

  [  
  {"type":"link", "caption":"MessengerPeople", "info":"https:\/\/www.messengerpeople.com"},  
  {"type":"postback", "caption":"Hello","info":"Hello"}  
  ]  

Category ID 1-10 or ID of a targeting list.

The lifetime of the content after publishing in seconds.

The id of the menu item holding the command that is used to pre-fill the users input field in WhatsApp in order to pull the content.

The name of the WhatsApp notification used for sending

A JSON array of parameters that are replaced in the WhatsApp notification

ISO 639-1 Language Code of the notification, that should be send. Defaults to the channel language if no default language for the notification template is set. Mandatory if parameter wb_notification is set

The name of the notification template

A JSON array of parameters that are replaced in the notification

The url of the header attachment. The following types/extensions are supported: image (jpg, png), video (mp4) or document (pdf). If the attachment is valid, a field called reusable_attachment is in the result, containing a cached URL for the sent file. Use this URL the next time for sending the same file to other users to improve the performance.

The text to be placed into the header variable

The suffix added to a dynamic link button

ISO 639-1 Language Code of the notification, that should be send. Defaults to the channel language if no default language for the notification template is set. Mandatory if parameter notification_template is set

The content ID

The ID of the content.

The ID of a single targeting list

Status Filter. Use 1 for listing only targeting lists that dont use a status filter and 0 for listing targeting lists that filter inactive users.

The targeting id

The name of the targeting list

A JSON array of the targeting list configuration

The name of the targeting

A JSON array of the targeting list configuration

The ID of the targeting list

The targeting id

The targeting query.

Schema:
{"query": {

"condition": "OR",

"rules": [{

"id": "rufnummer",

"field": "rufnummer",

"type": "string",

"input": "text",

"operator": "equal",

"value": "1234"

}]}}

The targeting id

Result should be grouped by messenger

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Return only the given KPI, run without to see all KPIs

Specify the source of the statistics, expected values: chats, tickets

Unit of period interval, expected values: hours, days, weeks

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Period of invoice, expected values: invoicing_period, last_invoicing_period
If set, this will overrule the parameters 'from' and 'to'

Group monthly active users by messenger

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Period of invoice, expected values: invoicing_period, last_invoicing_period
If set, this will overrule the parameters 'from' and 'to'

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Unit of period interval, expected values: days, weeks, months

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Unit of period interval, expected values: days, weeks

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Possible values json or csv.

UNIX timestamp of the start of the period, defaults to the last 30 days

UNIX timestamp of the end of the period, defaults to now

Filter the source of the URLS used for the clicks. Possible values: chats, content

Output order of the click information in descending order. Possible values: time, clicks

Possible values json or csv.

Specifies the unit of the result. Possible values are hours, days, weeks.

UNIX timestamp of the day/hour at which to start the statistics.
Default: Current day for hour statistics, 30 days ago for days or weeks

UNIX timestamp at which to end the statistics.
Default: current time

Possible values json or csv.

Specifies whether day statistics should be returned.
Default: 1 unless hour is set.

Specifies whether hour statistics should be returned.

UNIX timestamp of the day/hour at which to start the statistics.
Default: Current day for hour statistics, 30 days ago for days

UNIX timestamp at which to end the statistics.
Default: current time

Possible values json or csv.

Specifies whether day statistics should be returned.
Default: 1 unless hour is set.

Specifies whether hour statistics should be returned.

UNIX timestamp of the day/hour at which to start the statistics.
Default: Current day for hour statistics, 30 days ago for days

UNIX timestamp at which to end the statistics.
Default: current time

Include bot statistics.

Include additional week statistics.

The entity ID.

The entity ID

The entity data instance ID

The entity ID

The entity data instance ID, if the id is missing a new instance is created.

JSON with identifiers and attribute/value pairs for the object. Attributes which are not defined for the entity are ignored.
The keywords which identify the entitiy (in a message) are collected in the identifiers array. A keyword must not contain a ",".
Example:

{  
"identifiers": [  "john", "doe" ],  
"name": "John Doe",  
"mail": "john.doe@foo.bar"  
}  

The entity ID

The entity data instance ID

The widget ID. If omitted return old widgets, if 0 return all new widgets, otherwise just the widget with that ID.

The widget name.

The type ID of the widget

The widget title

The widget body text

Specifies whether a privacy check is displayed.

The widget privacy text.

The widget privacy link.

Requires JSON with a list of messengers used in the widget. info and link_text are optional
Example:

[ {  
"id": "WA",  
"link_text": "Please save the number",  
"info": "Please add the number to your contacts"  
} ]  

Requires JSON with a list of settings used in the widget. requires id and value
Example:

[  
{ "id": 1, "value": "FFFFAA" },  
{ "id": 5, "value": 14 }  
]  

Wdiget language. Per default the channel language is used.
de, en, es, fr, it, nl, pl, pt, ru, ar, tr, hr and jp

The widget ID

The widget name

The type ID of the widget

The widget title

The widget body text

Specifies whether a privacy check is displayed.

The widget privacy text

The widget privacy link

Requires JSON with a list of messengers used in the widget. info, link_text and sequence are optional
Example:

[ {  
"id": "WA",  
"link_text": "Please save the number",  
"info": "Please add the number to your contacts",  
"sequence": 1,  
} ]  

Requires JSON with a list of settings used in the widget. requires id and value
Example:

[  
{ "id": 1, "value": "FFFFAA" },  
{ "id": 5, "value": 14 }  
]

Wdiget language. Per default the channel language is used.
de, en, es, fr, it, nl, pl, pt, ru, ar, tr, hr and jp

The widget ID

Wdiget language. Per default the channel language is used.
de, en, es, fr, it, nl, pl, pt, ru, ar, tr, hr and jp

The widget setting name

The widget settings data type. Possible values are int, boolean, float, string, color.

The widget settings ID

The widget settings name

The widget settings data type. Possible values are int, boolean, float, string, color.

The widget settings ID

The ticket ID or user_id. Multiple ids can be separated by comma. If a user_id is specified the last ticket of that user is returned.

This is the amount of results that is returned. If the given amount is 0 the api will fallback to 500. The maximum is 500 if chats of the tickets are listed or 5000 if no chats are listed.

This is the amount of results skipped in the result set.

Field to order the results by. Valid values are 'id', 'closed', 'created', 'status', 'messenger', 'waiting_since', 'label_names', 'agent', 'last_chat', 'last_in', 'last_out'.

Whether to order the results ascending.

The status of the tickets. 0 for closed tickets, 1 for opened tickets

List only tickets assigned to me or my team.

The ID of a user or comma-separated list of IDs.

The ID of an agent or comma-separated list of IDs.

The ID of a label or comma-separated list of IDs.

List bot chat messages of the ticket.

A filter for searching tickets. Searches can be performed for ticket numbers, user ids, text in chat and notes. Only tickets of users are listed that match the search filter.

A filter for listing only tickets of users with this messenger. Valid values are 'WA', 'WB', 'FB', 'TG', 'IN', 'IM', 'VI'. (WA and WB are synonyms)

The maximum number of chats that are listed for each ticket .

A filter for listing only open tickets that are waiting since the specified time. Format: 0 for getting all answered, 1 for getting all unanswered tickets or from-to, e.g. 0-1552389233 or 1552389233-0 .

Set to 0 to avoid listing notes of the ticket(s) when ID is not specified.

List only new open tickets that have not been answered yet.

Include newsletters to tickets chat list.

Include custom fields of the user to tickets.

A filter for listing only closed tickets that are closed within the specified time. Format: from-to, e.g. 0-1552389233 or 1552389233-0 .

Include timestamps (last_in/last_out) for last inbound and outbound chat

Only show postponed tickets

Hide tickets that are postponed to the future

The ID of the user

The ID of a user.

The ID of a ticket or a user.

A note added. The agent must be logged in.

Array or comma-separated list of ticket ids. Use instead of the id parameter.

Array or comma-separated list of labels.

The ID of a ticket or a user.

The ID of an agent, to sign this ticket to.

The ID of a team, to assign this ticket to.

The email address of an agent, to assign this ticket to. Only works if agent id and team id are not set.

Set if you want to activate or deactivate the chatbot for a ticket. Only relevant if the chat for the ticket is locked.

Mark a ticket as answered even if the user send the last chat by setting waiting_since to 0.

Array or comma-separated list of ticket ids. Use instead of the id parameter.

Timestamp to postpone the ticket(s) to.

The ID of a ticket or a user

The ID of a label

Array or comma-separated list of ticket ids. Use instead of the id parameter.

Array or comma-separated list of label ids. Use instead of the label_id parameter.

The ID of a ticket or a user

The ID of a label

The ID of a ticket

The note text

Agent ID to use instead of the currently logged-in agent's ID

The ID of a ticket

The ID of a note to update

The updated note text

The ID of a ticket

The ID of a note to update

ID of a ticket to get statistics from

UNIX timestamp of the day/hour after which tickets have been created. Default last 24 hours

UNIX timestamp of the day/hour before tickets have been created

This is the amount of results that is returned.

This is the amount of results skipped in the result set.

If specified return only one line for each ticket with information about the last assigned agent even if multiple agents had been assigned.