Channel connectors
Last updated
Was this helpful?
Last updated
Was this helpful?
The following endpoints are part of the Connectors API. Channels are created by first installing a new connector. Connectors are responsible for linking the MessageBird Engagements platform to third party platforms. This documentation will provide details on how to interact with these endpoints.
A-Sync : this will start a background process that may require some time to complete. A Get call may be required to to retrieve the final result .
Currently we support creating the following channel connectors
connectorTemplateRef
string
Set as sms-messagebird:1
name
string
The name of your connector e.g. My SMS channel
arguments.phoneNumberId
string
The ID of the phone number to be installed. See
arguments.useCaseId
string
The ID of the use case. Required for 10DLC numbers. See
arguments.channelMessageType
string
The type of traffic that will be sent through this channel. It is a required field.
channelConversationalStatusEnabled
boolean
If true incoming messages will create new conversations in Inbox
To filter connectors by a certain channel type use the templateRef as below:
SMS
sms-messagebird:1
whatsapp:1
instagram:1
Facebook messenger
facebook:1
Telegram
telegram:1
Line
line:1
email-messagebird:1
Deleting a connector will also delete the associated channel. Messaging for the related channel connector will be interrupted. Be sure you want to delete the connector before proceeding
You can create a workspace subscription to listen to Channel Status changes and/or to be informed about new channel creations via webhooks
The example below will create a workspace wide subscription tracking all channel creations. this will inform you of any new channel being created and will return you the number / sender identifier
the connectorId
and the channelId
associated with it
The example below will create a workspace wide subscription tracking all updates regarding your channels. This is particularly useful when waiting for a channel to become active as a status update will always trigger an update event
Filter connectors by template ref
Limits the number of results to return
Pagination token that keeps of track of the current position in the list
Order in which to retrieve the results
Include internal ReleaseStatus in the result
To start receiving notifications via webhooks, the first step is to create a subscription. A webhook subscription specifies the destination URL for events and defines how they should be filtered. During setup, you can select which events to send to the specified URL. You can create multiple webhook subscriptions to route different types of events to various URLs as needed. Event filters are applied using AND operators, meaning that all specified criteria must be met for an event to be sent. If you want to handle multiple interactionTypes, you’ll need to create separate webhook subscriptions for each.
The ID for the workspace.
b4e02c85-c6d2-4b15-8885-e09671799c61
The ID for the organization.
cb28a94e-8557-4394-80ea-5bbd2170d434
{"someArgument":"someValue"}
Provide the arguments required by the security scheme(s) on the connector template.