Welcome to Our New API Docs! This is the new home for all things API (previously at ).
Communication Channels API
API for accessing users' email and SMS communication channels.
In this API, the :user_id parameter can always be replaced with self if the requesting user is asking for his/her own information.
A CommunicationChannel object looks like:
{
// The ID of the communication channel.
"id": 16,
// The address, or path, of the communication channel.
"address": "sheldon@caltech.example.com",
// The type of communcation channel being described. Possible values are:
// 'email', 'push', 'sms'. This field determines the type of value seen in
// 'address'.
"type": "email",
// The position of this communication channel relative to the user's other
// channels when they are ordered.
"position": 1,
// The ID of the user that owns this communication channel.
"user_id": 1,
// The number of bounces the channel has experienced. This is reset if the
// channel sends successfully.
"bounce_count": 0,
// The time the last bounce occurred.
"last_bounce_at": "2012-05-30T17:00:00Z",
// The current state of the communication channel. Possible values are:
// 'unconfirmed' or 'active'.
"workflow_state": "active"
}
This documentation is generated directly from the Canvas LMS source code, available .
string
A registration id, device token, or equivalent token given to an app when
registering with a push notification provider. Only valid for "push" type channels.
skip_confirmation
boolean
Only valid for site admins and account admins making requests; If true, the channel is
automatically validated and no confirmation email or SMS is sent.
Otherwise, the user must respond to a confirmation message to confirm the
channel.
communication_channel[address]
Required string
An email address or SMS number. Not required for "push" type channels.
communication_channel[type]
Required string
The type of communication channel.
In order to enable push notification support, the server must be
properly configured (via sns_creds in Vault) to communicate with Amazon
Simple Notification Services, and the developer key used to create
the access token from this request must have an SNS ARN configured on
it. Allowed values: email, sms, push