Terminology
| Term | Description |
|---|---|
| Message | A Message is a single outbound message. Messages get sent to handsets via various channels, and get marked as delivered if we receive confirmation of delivery, or failed if we don't. |
| Batch | A Batch is a collection of one or more messages. Each message that gets sent belongs to a batch, regardless of how many messages are contained within it. |
| Organization | This represents your organization, interacting directly with the Messaging Plus API. Organizations have an Organization API key that is used to authenticate against accounts related endpoints. |
| Account | Each Organization in mplus can contain multiple Accounts. Each Account has it's own Account API key, which is used to authenticate against message sending endpoints. |
| Delivery Receipt | Delivery receipts are status updates we provide on a per-message basis, with information about whether the related message has delivered, or failed to deliver. |
| Webhook | A Webhook (usually referred to as a Webhook request) is a HTTP request we'll make to your system after a specific event has triggered. The two types of events that can trigger webhook requests in mplus are Inbound messages, and Delivery receipts |
| Credit | Credit used for sending messages. 1 credit is equal to 1 message part. Credits can restrict accounts from sending depending on how the account is configured |
| Paid credit | Credits that can be topped up, and optionally go negative to an optional negative limit. Can be configured to automatically reset to zero on a fixed schedule |
| Packaged credit | Credits provided as part of a "package" to a customer. Tracked separate to paid credits, and can be configured to topup on a fixed schedule. Will always be consumed before paid credits |