Terminology
Understand the wording we use.
Term | Description |
---|---|
Access token | A JSON Web Token used to grant access to APIs. |
Account | Contains contact and billing information, and one or more API Spaces. |
API Space | A partition of the platform, containing isolated configuration and data. May also have isolated processing. |
App messaging | App or web based two-way messaging. |
App user | The end user interacting with a client SDK. |
Channel | Channel or route to which a message is delivered, for example, SMS, app messaging, Facebook. |
Conversation | Related, ordered set of messages with an ID and specific set of participants. |
Inbox | The ability to send push and content into an inbox inside a customer’s app or web site. Formerly known as Donky. |
Messaging API | The messaging component of the Enterprise Communications API, providing a unified messaging API able to send to any configured Channel, including SMS, Messaging, Inbox, and Facebook Messenger. |
Participant | Someone involved in a Conversation. May be an app user or a platform user. |
Platform User | Belongs to an account. Can log in to the portal and perform permitted actions. |
Profile | Information related to a particular app user or platform user. Can contain custom data and can also be used to access message history. |
Rules | Rules which define the platform functionality, for example, which channel should be used to deliver a message. |
Updated 6 months ago